Syncing a wholesaler's API into WooCommerce without overselling or melting the server

Short summary

A practical architecture guide for syncing a wholesaler's REST API into WooCommerce, treating the store as a derived cache rather than the system of record. Key decisions include declarative field mapping keyed on EAN/supplier index, dumb stock rules that hide unavailable products every cycle, margin logic applied above the pull layer, and split sync cadences with frequent stock/price polls and rare full-catalog refreshes. The same pull-map-protect-compute-schedule pattern generalizes to any ERP integration.

• •Treat WooCommerce as a cache with a checkout attached; the wholesaler is the system of record
• •Use declarative field maps keyed on EAN/supplier index, dumb stock rules, and split sync cadences to prevent overselling and server overload
• •The same architecture pattern applies to any ERP integration (Comarch, Dynamics, NetSuite) — only the data source changes

Generated with AI, which can make mistakes.