BAP Certification: Indonesian Shrimp Processors 2026 Guide

A floor-level, step-by-step playbook to set up BAP-compliant traceability and product segregation in Indonesian shrimp plants. Includes lot code examples, document control, mock recall targets, labeling controls, and the records auditors actually check.

If you run an Indonesian shrimp plant and plan to keep or win BAP business in 2026, traceability and chain of custody are where you pass or fail. In our experience, success isn’t about fancy software. It’s about clean master data, disciplined segregation, and labels that tell a consistent story from pond to pallet. Here’s the floor-level system we implement in plants that process both BAP and non-BAP shrimp.

The 3 pillars of BAP-ready traceability

Prove chain of custody at every handoff. A BAP claim is only as strong as the weakest document in the chain. You need a straight line linking finished goods to specific farms and harvest lots, with the correct star-level claim supported.
Segregate in a way auditors and buyers believe. You can use time or space. But you must control receiving, storage, production, rework, and packing so BAP input equals BAP output. Anything ambiguous gets downgraded to non-claim.
Reconcile fast. A two-hour mock recall target is realistic in Indonesia if your codes and records are tight. We aim for under 120 minutes with 100 percent lot reconciliation and named customers on the shipping side.

Takeaway: If one of these pillars is weak, you either lose the logo or the PO. Sometimes both.

A 12-week build plan that actually works

Weeks 1–2: Map, approve, and code

Process map. Sketch a simple, visual map from GRN to pallet dispatch. Mark risk points for mixing, rework, and labeling. Do this on the floor, not in a meeting room.
Supplier approval BAP. Verify each farm’s BAP status and star level in the GSA database. Record certificate numbers, species, and validity dates in a controlled supplier list. Require that POs for BAP shrimp explicitly state the claim and star level.
Receiving checklist. For BAP lots, collect farm certificate ID, harvest date, pond or lot ID, species, weight, and temperature. If any element is missing, receive as non-claim and segregate immediately.
Lot coding standard. Pick one code format and freeze it in a controlled SOP. A practical format that auditors love: Example: SHR-26041-A2-VN-HP-001
- SHR: product family (shrimp)
- 26041: Julian date (2026, day 041)
- A2: line or shift
- VN: species code (Vannamei)
- HP: process code (HLSO Peeled)
- 001: sequence or sub-lot Keep a key so anyone can decode it in 10 seconds. Train everyone to write and read the same way.

Weeks 3–6: Build controls where errors really happen

Segregation procedures. Choose a model that fits your plant. Physical segregation. Dedicated storage racks, color-coded totes and tags, separate thawing bins, unique knife and tray colors, and separate label stock vaults. Time segregation. Run BAP first after sanitation. Document purge, line clearance, and first-off checks. Record changeover start and end times with supervisor sign-off. Keep cleaning and purge logs in the batch file.
Rework controls. Rework inherits the status of the original lot. Never blend BAP rework into non-BAP runs. If you can’t prove lineage, downgrade it immediately.
Weigh-in and weigh-out. Capture raw intake weight by lot, WIP yields at each critical step, and finished case counts. Reconcile BAP input to BAP output by SKU in the production report. A simple mass balance table per run prevents hard conversations with auditors later.
Label management. Pre-approve all BAP label artworks, including star count and license number, and keep approvals on file. Case and pallet labels must carry the finished lot code. If you print the BAP logo on the case, the entire lot must be supported. When in doubt, leave the logo off and keep the claim in the spec and COA.

We often see mixed plants running shrimp next to finfish like Mahi Mahi Portion (IQF). The same segregation rules apply. Use color and time blocks so BAP shrimp never shares a tote, bin, or label roll with non-claim product.

Weeks 7–12: Test hard, digitize smart, and close gaps

Mock recall. Pick a finished lot and trace back to farm certificate ID and forward to named customers. Target under 2 hours. Include quantity reconciliation within 98–102 percent and copies of key records. Document start and end times, roles, and corrective actions.
Internal audit checklist. Walk the floor with your SOPs. Check receiving documents, storage signage, label vault control, changeovers, rework logs, weigh reconciliations, and dispatch paperwork. Raise CAPAs for every miss.
Digitize where it saves minutes. Many Indonesian plants hit BAP using controlled spreadsheets with barcode scanners. If you’re ready for software, tools we’ve seen work: Odoo with custom seafood modules, TraceRegister or iFoodDS for digital CoC, Maritech Seafood, and INECTA Seafood. Keep it simple. Scannable case labels and a shared drive with auto-backup beat a bloated ERP you don’t use.

If you want a quick sanity check on your codes, labels, and mock recall flow, Contact us on whatsapp. A 20-minute review often uncovers the one control you’re missing.

The records BAP auditors actually check

Supplier approval files with BAP certificates and star levels. Validity dates highlighted.
Purchase orders and contracts that specify BAP claims by lot or shipment.
Receiving records. Farm certificate ID, harvest or pond lot, temperature, weight, and pictures of labels if available.
Storage maps and segregation logs. Color codes or rack assignments for BAP and non-BAP.
Production batch files. Process orders, weigh-in/out sheets, rework logs, changeover cleaning, yield reports, and label usage logs.
Label control. Approved artworks with star count and license number, print logs, and destruction records for obsolete BAP labels.
Shipping documents. Case and pallet labels with lot codes, invoices, BOLs, COAs, and a claims register that states which shipments carried BAP claims.

If you can lay these out in a single evidence pack for one selected lot, you’re close to audit-ready.

Common questions we get, answered

How do we prove BAP-certified status when we process both certified and non-certified shrimp?

Run BAP as a distinct lot with documented segregation. Your proof is a chain of records: PO with BAP claim. Receiving with farm certificate ID. Segregated storage. Production batch file linking input lot to finished lot codes. Approved label proof and usage log. And a shipping document that carries the same lot to the customer.

Can I use mass balance for BAP claims, or do I have to fully segregate product?

Both can work if your buyer and claim allow it. Most retail on-pack claims expect full physical segregation from receiving through packing. Controlled mass balance can be acceptable for bulk or ingredient supply when inputs and outputs are reconciled tightly within the claim period. Confirm with your customer and the BAP claim policy before you promise it.

What lot code format works best for BAP-compliant traceability?

Use one code plant-wide that encodes date, line or shift, species, process, and a sequence. Keep it human-readable and printed on every case and pallet. Example again: SHR-26041-A2-VN-HP-001. Auditors care less about the exact format and more about your ability to decode it instantly and map it to documentation.

How fast should a mock recall be completed, and what proves success?

Target 2 hours end-to-end. Many auditors accept up to 4 hours, but we don’t bank on it. Success means you traced back to farm certificate ID and forward to named customers, reconciled quantities within 98–102 percent, showed copies of all key records, and documented corrective actions.

Which traceability software or spreadsheets are acceptable in Indonesia?

Auditors accept both if controlled. Spreadsheets must be version-controlled with locked formulas and time-stamped entries. For software, keep it practical. Odoo modules, TraceRegister, iFoodDS, Maritech, or INECTA work well when paired with barcode printers and handheld scanners. What matters is data integrity and speed of retrieval, not brand names.

How do I link finished product codes back to specific farms and harvest lots?

Your production order is the bridge. It references raw material GRNs with farm certificate IDs and the finished lot codes produced. Attach receiving documents to the batch file. Record yields, rework, and label runs on that same order. Now one folder links farm to finished pallet in seconds.

Case and pallet labels that protect the claim

Case label basics. Product description, SKU, net weight, production date, and finished lot code. Add an internal field for BAP status if you don’t print the logo.
Pallet label basics. Pallet ID or SSCC, SKU, case count, and the same finished lot code. If you use mixed pallets, never mix BAP and non-BAP lots.
BAP logo usage. Only print the logo and star count when the entire lot is supported. Keep the license number and approved artwork file in your label pack. No improvising on the packing line.

We apply the same label discipline on our Frozen Shrimp (Black Tiger, Vannamei & Wild Caught) lines. Tight controls on case and pallet labels save hours during customer verifications and recalls.

Five mistakes that kill traceability (and fast fixes)

Mixed rework. Fix. Tag rework by lot and status. Lock rework freezers. Downgrade questionable bins.
Label roll drift. Fix. Keep BAP label stock in a locked cabinet. Issue by lot with sign-off. Destroy leftovers and record it.
Vague POs. Fix. Force BAP claim language and star level on every PO and contract. No claim on PO, no claim on shipment.
Missing farm IDs at receiving. Fix. Train receiving to reject the claim and park the lot in non-BAP storage until documents arrive.
One person “owns” the system. Fix. Cross-train QA, production, and warehouse. Run joint mock recalls so no single point of failure exists.

Trends we’re seeing for 2026

Retailers want scannable case and pallet labels with GS1 barcodes to speed up their own verifications.
Buyers are asking for faster mock recalls and digital evidence packs, often before onboarding. A two-hour response is becoming the expectation.
Plants mixing species see more spot checks on label vaults and changeovers. Photographic evidence of line clearance is now common in audits.

Quick takeaways you can implement this month

Freeze a single lot code format and teach every supervisor to decode it.
Lock your label stock. Issue by lot. Destroy leftovers with a log and witness.
Run one cross-functional mock recall with a stopwatch. Fix the slowest link immediately.
Build a one-folder evidence pack for a pilot BAP lot. If you can pull every record in two minutes, you’re close.

We’ve helped Indonesian processors get from “we think we’re traceable” to “we can prove it in under two hours” without ripping out their systems. If you need a quick review of your floor controls or want templates for receiving and mock recalls, Contact us on whatsapp.