§00Integrations / Commerce
Commerce integrations: Orders in. Stock, shipments and refunds out.
Storefronts send events quickly and imperfectly. Shopify retries a webhook 8 times over 4 hours and promises no order, WooCommerce disables a webhook after more than five consecutive failures, and BigCommerce sends lightweight payloads that often carry only an ID. PartnerMCP verifies and de-duplicates every event, creates each ERP order exactly once, keeps stock in step and reconciles on a schedule.
Systems
5 · first interface · runs
- ShopifyGraphQL Admin API · CloudCloudOn-prem — integration page
- WooCommerceREST API v3 · Cloud · On-premCloudOn-prem — start an integration with WooCommerce
- Adobe Commerce (Magento)REST API (V1) · Cloud · On-premCloudOn-prem — start an integration with Adobe Commerce
- Amazon Selling PartnerSelling Partner API · CloudCloudOn-prem — start an integration with Amazon
- BigCommerceREST (v2 · v3) · CloudCloudOn-prem — start an integration with BigCommerce
What you can build.
Start from one of these, or describe your own. PartnerMCP plans every flow with the objects and interfaces of the systems you actually run.
- 01
Orders to ERP sales orders
SKU-level lines, taxes, shipping and discounts mapped to ERP parts; unknown SKUs are held for review instead of being created.
- 02
Inventory back to the store
ERP stock per location pushed to Shopify InventoryLevel with idempotent inventory
Adjust Quantities calls, or to each platform's inventory API. - 03
Fulfillment and tracking
ERP shipments become store fulfillments with tracking, including split and partial fulfillments.
- 04
Refunds and cancellations
Shopify refunds/create and cancellations become ERP credits and cancelled lines, with approval rules for large amounts.
- 05
Marketplaces
Amazon orders through the Orders API v2026-01-01, with ORDER_
CHANGE notifications delivered to Amazon SQS or EventBridge.
Pairings, step by step.
Each pair page has the plan, the field mapping and the edge cases for that combination.
Other categories.
A deal becomes an order, an order becomes a payment, and all of it lands in the warehouse. Integrations rarely stay in one category.
Product names and logos are trademarks of their respective owners. Their use indicates compatibility only and does not imply endorsement or partnership.
§04Start
Tell PartnerMCP what should connect.
Name your systems and describe what should happen. You’ll see the plan before anything is built.