A practical SIMP checklist for private-label tuna pouches from Indonesia entering the U.S. What to ask your cannery for, how to map every SIMP Key Data Element to real documents, timing by week, broker filing in ACE, and the mismatch traps that trigger NOAA holds.
If your shelf-stable tuna pouches keep getting pinged by NOAA holds, you don’t need more theory. You need a repeatable system. We took a U.S. private-label program from four SIMP holds in a quarter to zero in 90 days by tightening data at the lot level, aligning the broker’s ACE inputs, and eliminating the small mismatches that flag reviews. Here’s the playbook we use.
The 3 pillars of SIMP-ready private label tuna pouches
-
Lot-level SIMP completeness before production. Don’t wait for sailing. Lock the Key Data Elements (KDEs) per raw-material lot that will feed your pouch batch. When the cannery blends, every vessel/lot that contributes must be traceable end to end.
-
Immutable lot-to-label-to-entry crosswalk. Your retail label claim, internal batch code, cannery production lot, and the SIMP package quantity must reconcile. We maintain a “KDE crosswalk” that ties weights, species, gear, FAO area, and vessel IDs to the final commercial documents.
-
Broker alignment and ACE dry-runs. Your customs broker can file SIMP in ACE, but they can’t guess your KDEs. Give them a clean template in the exact fields they submit. We do a pre-ETD dry-run for the first three shipments to catch gaps early.
Practical takeaway: Write these three pillars into your PO terms. Make SIMP data delivery a condition of production start, not shipment release.
Weeks 1–2: Validate your supply and data sources (tools + templates)
Start upstream. SIMP applies to tuna regardless of product form, so shelf-stable pouches absolutely qualify. The importer of record must hold a valid International Fisheries Trade Permit (IFTP) and retain records for two years. With that in mind:
- Confirm species and fisheries. Most Indonesian tuna pouches use Skipjack (Katsuwonus pelamis) or Yellowfin (Thunnus albacares). Typical FAO areas are 71 (Western Central Pacific) or 57 (Eastern Indian Ocean). Ask your cannery which applies to each lot.
- Verify vessel identity. Prefer an IMO number. If the vessel is smaller and lacks IMO, capture the national UVI/registration and flag state. Cross-check names and IDs against RFMO lists (WCPFC, IOTC) and ensure the vessel isn’t on any IUU list. In our experience, 3 out of 5 SIMP queries begin with vessel or flag mismatches.
- Clarify gear type. Purse seine, pole-and-line, or longline are common. Whatever your marketing claims, your SIMP gear must match. If you plan to print “pole-and-line” on the pouch, don’t accept any purse seine inputs in that batch.
Template setup we recommend:
- KDE Master Template (per raw-material lot): Vessel name/ID, flag, gear, catch date range, FAO area, landing port/date, transshipment details (if any), raw weight by species, supplier chain handoffs.
- Crosswalk Sheet (lot to finished goods): Raw lots consumed per batch, cooked/retort yield assumptions, finished pouches per lot, net weights used in customs vs internal records.
Need help mapping your cannery paperwork to SIMP fields? We’re happy to review your first template and point out gaps. Contact us on whatsapp.
Weeks 3–6: Build your SIMP data pipeline and test it
This is where most programs get traction. We map each SIMP Key Data Element to specific, real documents you can demand and file:
- Species and scientific name. Cannery raw material receiving log, purchase contract, and QA intake sheet.
- Product form/quantity. Cannery batch record, finished goods report, export invoice and packing list. Use consistent net weights. Don’t swap drained weight into SIMP unless that’s how your broker files.
- Harvest date or date range. Vessel logbook summary or cannery lot sheet referencing trip dates. Keep it realistic. We’ve seen month-long ranges trigger questions when the vessel trip was seven days.
- Gear type. Cannery lot sheet or supplier declaration referencing the vessel license. If you say pole-and-line, document it.
- Area of harvest. FAO area code on supplier declaration or landing receipt. For Indonesia, FAO 57 or 71 are most common. Match the vessel’s RFMO area.
- Vessel flag state and ID. Vessel license, IMO certificate, or national registration. Record exact spellings and any recent name changes.
- Transshipment info. If at-sea transshipment occurred, you need the RFMO transshipment declaration and authorization. For port transshipment/landing, secure the landing receipt and port authority document.
- Chain of custody. Capture every entity from vessel to cannery to exporter. Use bills of lading, delivery notes, internal transfer sheets, and cannery receiving logs to keep the chain unbroken.
- Importer credentials. IFTP number, Importer of Record name/EIN. Your broker will pull this into the ACE message set.
Two non-obvious things that prevent holds:
- Harmonize weights now. Define how raw weight converts to finished pouches. If your CBP entry shows 10,000 kg of goods and your KDE roll-up only explains 9,200 kg of raw input, expect questions. We keep a transparent yield table in the crosswalk.
- Freeze your codes. Lock style codes, UPCs, and internal batch IDs early and keep them consistent across label art, batch records, and commercial invoices. NOAA often spot-checks code consistency.
If your private label program also sources raw tuna components for co-packing, ensure those inputs are already “SIMP-ready.” We routinely prepare KDE-backed items like Yellowfin Ground Meat (IQF) and Skipjack Cube (WGGS / IQF) for customers who need tight upstream traceability before retort.
Weeks 7–12: Broker integration, mock audits, and scale-up
- ACE dry-runs. Have your broker key a mock SIMP message from your template and confirm field mappings. Yes, brokers can submit SIMP data in ACE, but you own accuracy.
- PO clauses. Bake SIMP into contracts. We use: “Supplier will provide complete SIMP KDEs per raw lot at least 10 business days before ETD. No substitution or blending without written approval and revised KDEs. Failure delays payment and shipment release.”
- Mock audit. Pick one shipped lot each month. Rebuild the chain from vessel to entry and check every date, weight, and code. You’ll find small inconsistencies before NOAA does.
- Scale. Once your first three POs clear cleanly, standardize the template, schedule pre-ETD checks, and roll to more SKUs.
The 5 mistakes that kill SIMP entries
- Drained vs net weight confusion. Your customs entry uses one number. Your SIMP roll-up uses another. NOAA holds the file.
- FAO area off by one. Indonesia resonates with FAO 57 or 71. If your vessel fishes both, split lots or document the portion from each.
- Gear code doesn’t match the label claim. Marketing says pole-and-line. SIMP says purse seine. Instant query.
- Missing transshipment paperwork. If any at-sea transfer happened, RFMO documentation is mandatory. No exceptions.
- Species or HS code mismatch. Tuna pouches are classified as prepared/preserved tuna. If your entry classification implies fresh/frozen, expect questions.
Practical fix: Keep a single-page “KDE-to-Commercial Crosswalk” with the shipment. Our clients attach it to the document set for the broker and it cuts questions by half.
Common questions we get, answered quickly
Does SIMP apply to shelf-stable tuna pouches from Indonesia?
Yes. SIMP is species-based. Tuna is covered regardless of form, including retort pouches.
What exact data do I need from the cannery to pass SIMP for tuna?
Per raw lot used in your pouches: species/scientific name, gear type, FAO area, catch date range, vessel flag and ID (IMO or national registration), landing or transshipment documentation, and chain-of-custody records into the cannery. Plus finished goods weights and quantities that reconcile to your entry.
Who is responsible for SIMP filing—the brand, the supplier, or the customs broker?
The importer of record. Your broker can submit the SIMP message in ACE, but legal responsibility sits with the importer. Your supplier must furnish accurate KDEs and documents, and you must retain them for two years.
How do I verify an Indonesian tuna vessel’s ID or flag for SIMP?
Ask for the IMO number first. If not available, use the national registration/UVI with the flag state. Cross-check the name/ID on RFMO authorized vessel lists and confirm it isn’t on any IUU list. Watch for recent vessel name changes and expired licenses.
What happens if my SIMP data doesn’t match the customs entry?
NOAA can place the shipment on hold or request additional documentation. We see this when weights don’t reconcile or the FAO area/gear code conflicts with the label or invoice. Fix by issuing a corrected SIMP set and, if needed, an entry correction with your broker.
Is MSC or dolphin-safe certification enough to satisfy SIMP?
No. They’re different programs. Those logos don’t replace SIMP KDEs or filings.
How long do I need to keep SIMP records for tuna imports?
Two years from the date of entry into U.S. commerce.
Resources and next steps
If you only do one thing this week, build your lot-level KDE template and demand it before production. By Week 6, you should have a functioning crosswalk that ties raw lots to pouch SKUs and clean ACE submissions. By Week 12, your mock audits should be boring. That’s when SIMP stops being a fire drill and becomes routine.
Questions about your project or want a quick sanity check on your template? Call us. If you’d like us to review a sample KDE set against your pouch BOM and broker inputs, Contact us on whatsapp. We’ll tell you exactly what will trigger a hold—and how to prevent it, before the container sails.