Building products on Shopify: sync NetSuite bundles, pieces and saleable stock

What this looks like in building products manufacturing

A manufacturer offers trim products through dealers and a direct Shopify store. The store sells a bundle, while the ERP tracks individual lengths. A finish option uses the same base material but cannot be fulfilled from unfinished stock. Publishing the warehouse’s physical piece count as store bundles overstates availability and ignores the finishing step. A useful integration resolves the variant and pack definition, calculates the eligible quantity under inventory’s policy, and preserves the conversion used on each accepted order.

Records, ownership, and update rules

Work through the process

1. 01
   Inventory the unit conventions

   Review representative dealer and direct orders to identify where units differ. Define conversions with the product owner rather than deriving them from product titles. Where a custom dimension prevents a fixed conversion, route the order through an explicitly reviewed calculation.
2. 02
   Map finishes and readiness

   Distinguish finished saleable stock from unfinished base material or stock reserved for another process. Tie the availability rule to the correct variant. A common material family does not make every piece eligible to satisfy every finish or size request.
3. 03
   Preserve the commercial quantity

   Keep the original bundle or carton quantity with the conversion used when the order was accepted. Store the calculated base quantity separately. This gives customer service a clear explanation when ERP and storefront quantities look different but represent the same order.
4. 04
   Validate the exact commerce operations

   Test the intended product update, quantity publication and order handoff with the configured permissions. Confirm separately how cancellations and partial fulfillment are handled. A successful product-field update does not establish that every order action is available.
5. 05
   Reconcile catalog and event changes

   Test a revised pack definition, a repeated order message and a late update. Compare authoritative order state before applying older information. Reconciliation should preserve accepted historical conversions while allowing approved future catalog changes.

Handle the exceptions explicitly

A bundle size changes after existing orders

Keep the old conversion on accepted orders and apply the new definition only to the approved future scope.

A product is sold by area but cut to order

Require the reviewed dimension and rounding rules. Do not infer manufacturing yield or saleable quantity from area alone.

Finished stock is moved to a quality hold

Recalculate eligible availability and expose affected accepted orders for the responsible owner to review.

What to verify before expanding

• A storefront bundle maps to the approved base quantity without losing the original unit.
• Unfinished or held stock cannot inflate the published variant quantity.
• Historical orders keep their accepted pack definition after catalog changes.
• Repeated messages retain one destination order and do not double demand.

Technical references

• Oracle NetSuite: using external IDs
• Shopify: webhook ordering and reconciliation