Skip to main content
Adding a warehouse or 3PL to the Sync Server is a catalog entry, not a code change. A connector is a JSON definition — auth, endpoints, pagination, cursors — plus one or more mapping rule sets, run by a generic runtime through the same resilience, ingestion, checkpoint and crash-safe submission machinery every hand-written integration uses.
Hand-written integrations are reserved for the strategic platforms where depth justifies compiled code — Shopify, NetSuite, Amazon, DCL. Everything else is a definition, and existing per-partner code migrates by attrition: when one needs a fix, it is ported to a catalog entry rather than patched.

​
What a definition carries

A definition in outline:

​
dedupPolicy — read this before shipping a push flow

An ambiguous failure is a timeout or dropped connection where the remote may already have accepted the order. You cannot tell from your side whether it did. One field decides what happens next, and it drives all three layers — transport retries, the submission guard, and the stale-in-flight watchdog — so they can never disagree with each other.
The wrong answer here is how duplicate shipments happen. Choose safe_to_retry only when you have proof the remote deduplicates — a documented idempotency key it honours, not an assumption that a second identical order would be rejected. A dedup claim without idempotencyHeader still gets exactly one send, because the platform will not take your word for it.
The default parks the order rather than retrying, which means a real outage produces a queue of orders awaiting review instead of a queue of possible duplicates. That is the intended trade: a human looking at ten parked orders is cheaper than a customer receiving two shipments.

​
Shipping one

A catalog entry ships with golden fixtures, so a mapping change that silently drops a field fails review rather than production. Several long-tail ports have found long-standing silent mapping failures in the code they replaced — fixtures are the reason.

​
Next steps

API contract

Envelopes, error codes and correlation ids.

Troubleshooting

Circuit breakers, stuck orders and rate limits.

gRPC dispatch

Getting orders into the Sync Server durably.

gRPC flow

What happens to an order once it is accepted.