Define the canonical item master schema covering shared fields (SKU, description, price, unit of measure, tax class, weight, images, active status) and map ERP internal field names to ecommerce platform API field names before writing any code.
Set up a change-detection mechanism in the ERP: either poll an item change log or audit table at a defined interval, or subscribe to a change event/webhook if the ERP supports it (e.g., SAP Change Pointers, Oracle Business Events, Dynamics 365 data events).
For each changed item record, transform the ERP payload to the ecommerce API schema, handling unit conversions, HTML formatting of descriptions, and multi-value attributes (e.g., variants, categories).
Upsert the item via the ecommerce platform's product API using the ERP's internal item ID or SKU as the external reference key; use a conditional PUT or POST-with-deduplication to avoid creating duplicates.
Log each sync attempt with the source ERP item ID, target platform ID, timestamp, and outcome; retain failed records for retry and alerting.
Known gotchas
Price and currency handling requires explicit mapping between ERP price lists and ecommerce price books; syncing the wrong price list (e.g., wholesale instead of retail) can cause incorrect storefront pricing without an obvious error.
Deleting or deactivating an item in the ERP should set it to 'archived' or 'draft' in ecommerce rather than hard-deleting it, to preserve order history and SEO URLs.
Image assets are typically stored outside the ERP; the sync pipeline must handle image URL generation or file transfer separately from the structured data sync, as ERP records usually only store image file names or paths.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp