NetSuite–Postgres Sync for Food Brands: Reconcile Co-Packer Receipts and Finished-Goods Records

What this looks like in packaged food and snacks

A co-packer reports 500 finished cases while the receiving team accepts 492 and holds eight for inspection. A spreadsheet currently changes the supplier figure to match the warehouse. That removes the reason for the difference. An operational view should retain all three quantities and distinguish received, accepted, and held states.

Records, ownership, and update rules

Work through the process

1. 01
   Choose the receipt identity

   Link the supplier notice to the expected purchase or production receipt using approved references. Similar dates and quantities can suggest candidates but cannot establish the business relationship alone.
2. 02
   Keep states separate

   Model the supplier’s reported quantity, the warehouse count, and the accepted ERP quantity independently. A hold is an operational state, not evidence that the supplier shipped fewer goods.
3. 03
   Expose the discrepancy

   Calculate differences at the correct item and unit grain. Include pack conversion and source timestamps so an analyst can tell a real shortage from an incomplete receipt update.
4. 04
   Apply a reviewed correction

   Let receiving or the authorized ERP owner decide whether to correct a record, accept a partial receipt, or request supplier evidence. Read back the result and retain the original discrepancy history.
5. 05
   Replay the 500-case receipt and its revision through Postgres

   Start with the scenario: a co-packer notice for 500 cases, 492 accepted in NetSuite, eight held. Query the Postgres reconciliation row and confirm four separate columns carry those values with a source timestamp each. If a column has been merged into another, or the supplier figure now reads 492, stop the rollout. Next, insert a correction proposal in Postgres against the accepted quantity and reread the NetSuite item receipt; it must still show 492 until the authorized ERP owner approves. Then load a revised co-packer notice for the same shipment. Postgres should keep both revisions side by side, and the accepted receipt must remain untouched.

Handle the exceptions explicitly

Supplier revises its notice

Version the document and compare the revision with the accepted receipt before changing the case.

Warehouse counts units, supplier sends cases

Use the approved conversion and preserve both original quantities.

Held goods are later accepted

Append the approved release and receipt evidence rather than rewriting the earlier inspection state.

What to verify before expanding

• Supplier, received, accepted, and held quantities remain distinguishable.
• A database correction proposal cannot silently change an accepted receipt.
• A revised co-packer notice remains distinguishable from the original notice and does not overwrite an accepted ERP receipt.
• Releasing previously held goods adds the new approval and receipt evidence while preserving their earlier held state.

Technical references

• Stacksync two-way sync quick start
• Stacksync NetSuite supported objects