3PL and WMS integration expansion
The integration catalog grew from 162 to 182 integration ids, with 20 long-tail 3PL integrations added:accion, aplin, coghlan, evobox, expeditors, fillogic,
fulfillment247, haul_and_store, interfulfillment, invenco, its_logistics,
metro_supply_chain, omnipack, outerspace, pro_fs, quiver, red_stag, valencia,
verde, and visible. Each is wired through config, concurrency limits, job kinds, routes,
and webhook handlers.
Counting platform-backed and long-standing modules, the sync server carries roughly 155
3PL/WMS integrations in total.
Verification status
Integrations are not all equal, and the difference matters when you’re planning an onboarding. A verification matrix (researched 2026-07-20 against vendor sites, developer portals, and middleware integration guides) classifies each:
Verified against public docs:
Platform-backed — prefer the underlying service:
Agent tool planning
/agent/execute endpoint: plan decides what to call,
execute runs it.
Reconciliation and catalog APIs
Order submission reliability
- Failed submission attempts are counted per backend, so a backend that is failing consistently is visible rather than hidden behind aggregate retry noise.
- Exponential backoff with a max-attempt cutoff on order submission retries, replacing unbounded retrying.
- The full upstream error chain is logged on submission failure — the root cause is no longer collapsed into a generic message.
Multi-tenancy and channels
- Organization-tenant mapping — an organization can now map to its tenants.
- TikTok retailer code support.
- TryNow partial-payment order handling.