A practical, step-by-step FSMA 204 playbook for Indonesian chili pepper exporters. How to map KDEs to your harvest, cooling, and initial packing processes. How to assign traceability lot codes for mixed-farm loads. And what your US importer will expect in 2026.
I went from paper folders to importer-approved FSMA 204 readiness in 90 days using this exact system. That was three harvest cycles of chili peppers in West and Central Java, with dozens of small farms, one packhouse, and two cold rooms. If you export peppers to the US, here’s the no-nonsense version of what worked.
The 3 pillars of fast FSMA 204 compliance
Pillar 1. Map your process to FDA’s Critical Tracking Events (CTEs). Harvest, cooling, initial packing, shipping, receiving, transformation. If it happens in your chain, you need the associated Key Data Elements (KDEs).
Pillar 2. Standardize one traceability lot code (TLC) system. Assign the TLC at initial packing and link every upstream harvest to it. Use a GS1-friendly format so it scales with labels and EDI later.
Pillar 3. Capture data with simple tools your team will actually use. Excel or Google Sheets, QR labels on cartons, and WhatsApp photo drops for field and dock evidence. Fancy software can come later.
Week 1–2. Validation and scope
Are fresh chili peppers covered by FSMA 204? Yes. Fresh peppers, including hot peppers like cayenne and other chilies, are on the FDA Food Traceability List. That means harvest, cooling before packing, initial packing, shipping, receiving and any transformation require KDE records. Dried chilies and shelf-stable sambal are not on the list, but if you transform fresh peppers into those products, you must keep the transformation KDE at your facility.
What’s the deadline? January 20, 2026. In the last six months, FDA has continued issuing FAQs and small clarifications. Nothing has moved the date. Plan to be audit-ready by Q3 2025. That gives you time to fix gaps.
Scope your supply chain. List your farms, harvest crews, field locations, cooling points, packhouse lines, consolidators, exporter, US importer. Identify CTEs you control versus your partners. Our rule of thumb. If you touch the product before it leaves Indonesia, assume you owe records.
Takeaway. Confirm peppers are in scope. Define every node. Decide who will assign the TLC. For most exporters, that is the initial packer.
Week 3–6. Build your MVP system and test it on one lane
What records do I need at harvest and initial packing for peppers?
Harvest KDEs to capture.
- Commodity and variety. Example. Fresh hot pepper, cayenne.
- Harvest date.
- Field location description. GPS or a mapped block. Example. Desa Cibogo, Block A3, -6.822, 107.639.
- Harvesting firm name and contact.
- Quantity and unit for each harvest batch. Example. 420 kg in field crates.
- Reference document. A harvest ticket or WhatsApp photo with date stamp works if it links to your sheet.
Cooling step KDEs (if you cool before initial packing).
- Cooling date and location.
- Inbound reference to harvest lots cooled.
- Quantity cooled. Product identifier.
Initial packer responsibilities.
- Assign the Traceability Lot Code (TLC) for the packed units.
- Record pack date, facility location, product identity, unit of measure, quantity, and the list of harvest lots or cooled lots included in that TLC. This is where most exporters struggle because of mixed-farm loads.
How do I create one traceability lot code when I combine peppers from multiple small farms?
Use a TLC that is human-readable and GS1 friendly. Our format.
- Company prefix. IV for Indonesia-Vegetables or your GS1 company number.
- Facility code. PKH01.
- Pack date in YYYYMMDD.
- Line or shift code. L2.
- Sequence. 001.
Example TLC. IV-PKH01-20250115-L2-001.
If you use GS1, encode GTIN plus lot. On a case label use Application Identifiers. (01) GTIN, (10) Lot, (21) Serial optional for case-level. Example. (01)10812345001234 (10)PKH01-20250115-001.
The key is linkage. In your initial packing sheet, link TLC IV-PKH01-20250115-L2-001 to all harvest tickets used. That can be ten farms. You are allowed to commingle. You just need the full cross-reference.
Low-cost data capture that actually works
- Excel or Google Sheets with dropdowns for farm, field, product, and a protected TLC generator tab.
- QR labels on cartons that hold the TLC and GTIN text. Print with a desktop thermal printer.
- WhatsApp photos from the field or dock saved to a shared folder. The photo filename is the harvest ticket number and date. It is crude but auditors accept it when it is consistent.
We’ve done this on fresh hot peppers and on export-grade Red Cayenne Pepper (Fresh Red Cayenne Chili). The same spine works for other FTL products like tomatoes and cucumbers.
Takeaway. Keep it simple. One TLC per pack run. Rigid linkage to all harvest batches. QR labels reduce transcription errors.
Week 7–12. Scale, add shipping records, and align with your US importer
What does a compliant shipping record to my US importer look like?
For each shipment, include.
- Shipper and receiver names, addresses, and contact.
- Ship date and receiving date (estimated is fine on the outbound record).
- Product description. Fresh chili peppers, cayenne, 5 kg cartons.
- Quantity and unit. 1,200 cartons.
- All TLCs in the shipment. List or attach a file.
- Transporter name and conveyance ID. Container and seal numbers for sea freight.
- Your traceability plan reference. A short SOP filename or code.
Hint. Put the TLC list as a CSV attachment called TLC_manifest.csv. Your commercial invoice and packing list should reference it. Many US importers under FSVP will test you by requesting these within 24 hours. Practice a 4-hour turnaround.
US importer FSVP coordination. Share your traceability plan and a redacted example shipment file with your importer before the first 2026 load. Agree on file formats. Decide who responds if FDA requests records at the border. We usually designate the importer as the FDA contact with us as the record custodian in Indonesia.
Do mixed vegetable cartons with peppers count as transformation under FSMA 204?
Yes. If you create a new food by mixing peppers with other vegetables, that is a transformation CTE. You must record transformation KDEs. Input TLCs used, transformation date and location, output product identity and quantity, and the new TLC for the mixed item. For example, building a stir-fry blend similar to our Frozen Mixed Vegetables requires a transformation record. If the finished food is not on the FTL, downstream shipments of the finished item are not covered, but your transformation event still is.
Does FSMA 204 cover dried chilies or sambal products?
Dried chili peppers and shelf-stable sambal sauces are not on the FTL. However, if you receive fresh peppers that are on the FTL and then transform them into a non-FTL food, you must keep transformation KDEs at your facility. That includes the input TLCs and the output description. Downstream buyers of the dried or shelf-stable item are outside FSMA 204.
Takeaway. Shipments of fresh peppers need shipping KDEs. Processing fresh peppers changes the CTEs you must keep, even if the output is off-list.
The 5 biggest mistakes we see and how to avoid them
- Assigning different TLCs to the same pack run. Use one TLC per continuous pack run of a uniform spec. Change the TLC only when you stop and change date, line, or spec.
- Ignoring cooling records. If you hydro-cool or forced-air cool before initial packing, that is a CTE. Capture the cooling KDEs. Link harvest to cooling to initial packing.
- Missing field location details. “Farm A” is not enough. Use a GPS pin, block map, or a clear plot code. We add a simple field sketch page in the traceability plan.
- Treating QR labels as decoration. A scannable QR that embeds GTIN and lot saves you at shipping. It also lets your importer verify TLCs at receiving.
- Assuming a small-farm pass. There is no general small-business exemption in FSMA 204. Most Indonesian aggregators and packers that export to the US are in scope.
Am I exempt if I’m a small Indonesian farm aggregator?
Usually no. FSMA 204 does not include a broad size-based exemption for firms shipping FTL foods into US commerce. Certain narrow exemptions exist. Direct-to-consumer sales and some scenarios outside the rule’s scope. Those do not apply to export programs moving product into US distribution. If you are aggregating from smallholders and initial packing for export, plan to comply.
Quick answers to questions we get weekly
- What is a TLC source reference for peppers. It is the name of the entity that assigned the TLC. On your records, note “TLC assigned by PT FoodHub Collective Indonesia, Packhouse PKH01.”
- How to link harvest batches to the initial packing TLC for peppers. In your pack sheet, list each harvest ticket ID, date, field, and quantity that fed into the TLC. Keep a one-to-many linkage table.
- Field location description examples for pepper harvesting KDE. “Kabupaten Garut, Desa Mekarsari, Block C7, GPS -7.2341, 107.8912.” Or a farm map code like “Farm ID 108, Plot C7 per 2025 field map.”
- Timeline to comply by January 2026. Run a pilot in Q2, scale in Q3, dry-run an FDA-style 24-hour record request in Q4. You will sleep better.
If you want a sanity check on your TLC format or KDE sheets, you can Contact us on whatsapp. We’re happy to look at one lane and point out risks.
Resources and next steps
- Build a 2-page traceability plan. It should describe your product list that is on the FTL, CTE map, who assigns TLCs, your coding schema, where you store records, and your 24-hour response process. Keep it short so people read it.
- Create three templates. Harvest ticket, cooling record, initial packing log. Add a shipping manifest that lists TLCs and a receiving log for your US partner to mirror.
- Test with one product. Fresh cayenne peppers. If you need a pepper spec to align your data capture, our Red Cayenne Pepper (Fresh Red Cayenne Chili) page is a good starting point for unit, grade, and handling details.
Questions about your pepper program and importer expectations. Call us. A 15-minute review usually saves weeks of back and forth later.
Our experience shows that simple systems win. Keep the records tight, the TLC consistent, and your importer looped in. That is how you hit January 2026 with confidence.