Melty Veggie sticks

Name: Melty Veggie sticks
Brand: Organix

Organix

5024121317125

Processing

–

Not recorded

A gap in the source, not a sign it is unprocessed

Additives listed

None we have assessed

Counted from the label, not by quantity

Fat per 100g

8.60g

Medium

UK FSA front of pack threshold

Three separate readings, kept apart on purpose. This is not a score, and none of it says this product is harmful.

Additives

No additives listed in the source data for this product. That can mean it genuinely has none, or that the entry is incomplete. The pack itself is the authority.

Ingredients

No ingredients list against this barcode. Another pack of the same product, 5024121308123, lists what follows. It is a different pack, so read it as a guide to the recipe and not as this pack's own label.

Corn Dried green peas Sunflower oil Rice flour Tomato powder Sweetcorn powder Thiamin (vitamin B1)* TOTAL 60.7% 19.4% 7.0% 6.5% 4.3% 2.1% <0.1% 100% *Thiamin (vitamin B1) has no organic certification. ALLERGY ADVICE: Gluten free.

Processing level

No processing group recorded for this product. That is a gap in the source data rather than a sign the product is unprocessed.

Nutrients per 100g

Fat

8.60g

Medium

Saturates

Low

Sugars

3.60g

Low

Salt

0.01g

Low

Judged on the UK FSA front of pack thresholds for solid foods. A dash means the source has no figure, which is not the same as a low one.

Other packs of this product

Open Food Facts keeps a record for every barcode, so one product can appear several times. Each of these carries its own data, and may be fuller or thinner than this one.

Melty Veggie Sticks
5024121308123 no processing data

Where this came from

Product data from Open Food Facts, which is crowd sourced and can be incomplete or out of date. Photograph from the same source, under the Creative Commons Attribution ShareAlike licence. Open Food Facts last changed this record on 27 March 2026, and our copy is from 20 August 2026. The source is checked every night, and a product is rewritten here only when its record there changes. Something wrong? Correcting it at the source fixes it here and everywhere else that uses the same data. If the problem is one of our additive assessments, tell us.

Scan another barcode Search