What you do
Create an Integration in the Commerce Admin with REST API access, and share the credentials it produces.

Defined in your admin, scoped to what it needs, revocable by you.
Adobe Commerce and Magento Open Source do not expect you to hand a fulfillment provider a user account. Defining an Integration in the Commerce Admin establishes where the OAuth credentials and redirect URL live, and identifies exactly which API resources the integration may reach. Third-party applications authenticate with OAuth 1.0a.
One integration, defined once, in your own admin.
Create an Integration in the Commerce Admin with REST API access, and share the credentials it produces.
Orders, shipments and product data. There is no reason a fulfillment integration needs anything broader.
Mapping, SKU matching, test orders and go-live, connecting directly to the warehouse management system. Live the same business day.
If a pre-built connector does not fit, the position is that OC3PL builds the connection, and custom integrations are company funded.
An integration user with REST API access — created as an Integration in the Commerce Admin, which establishes the OAuth credentials and identifies the API resources the integration may use. Third-party applications authenticate with OAuth 1.0a. The connection runs directly to the OC3PL warehouse management system and is live the same business day.
Orders, shipments and product data. Magento lets you scope an Integration to specific resources, and a fulfillment integration has no reason to reach customer or payment data beyond what an order carries. Scoping it narrowly at the start is easier than auditing it later.
Magento supports REST, GraphQL and SOAP, so a connection is usually possible even where a pre-built connector does not fit. Where it does not, OC3PL’s position is that if a connection does not already exist the in-house team builds one, and those custom integrations are company funded. Raise the requirements early in onboarding rather than at go-live.
The detail behind this, in OC3PL’s own guides.
How OC3PL connects to Magento and Magento 2 — a direct warehouse management system link, the REST API access it needs, and same-day turnaround.
What connecting a store to OC3PL actually involves: one warehouse management system, an API key or app install from you, and mapping, SKU matching and test orders from us.
Discover why a flexible API is critical for scaling e-commerce brands. Learn how custom API support from a 3PL solves complex fulfillment challenges.
Discover the risks of poor 3PL integration, including fulfillment errors, inventory issues, and support tickets, and why a tech-forward partner is key.
How to move your store’s fulfillment connection to a new 3PL without losing orders: the test sequence, what to run in parallel, and what to confirm before you cut over.
Experiencing 3PL Shopify integration problems? Learn how to diagnose and fix common 3PL syncing issues related to APIs, data, and rate limits.
Tell us your Magento version and any customisation, and we will confirm what the integration needs.