Send eligible orders
The current automatic workflow is limited to orders whose fulfillment method is shipping. Pickup and local-delivery orders stay out.
Why Use ShipStation with CMS Max?
Native fulfillment integration
Keep the storefront and order record owned while ShipStation runs the shipping desk.
The native CMS Max integration sends eligible shipping orders to ShipStation and uses a secret-bearing webhook to return shipment status and tracking. Carrier, label, batch, and warehouse work remains in the provider workspace.
- Shipping orders only
- Queued handoff
- Secured webhook
- Tracking returned
Decision frame
Use ShipStation when a dedicated fulfillment workspace reduces re-entry.
The integration is useful when the team needs a governed transition from a direct CMS Max order to carrier and label operations, then a reliable return of shipped status.
Operate in ShipStation
The provider account owns carriers, services, labels, batches, manifests, returns, warehouse operation, and related billing.
Return the final state
A secured SHIP_NOTIFY webhook lets CMS Max retrieve the shipment, match the order, store tracking, and mark fulfillment complete.
Platform and operating capability
The native connection has a clear two-system contract.
Each system keeps the responsibilities it is designed to operate.
Order eligibility
CMS Max evaluates plugin status, automatic sync, credentials, and the shipping fulfillment method before handoff.
Shipment payload
Order number, addresses, items, SKUs, quantities, amounts, notes, origin, and package context are mapped for the provider.
Queued processing
The handoff runs as an application job so failures and retries can be monitored operationally.
Provider fulfillment
Staff choose carriers, services, packages, labels, batches, manifests, and other available ShipStation tools.
Shipped callback
ShipStation posts the event to the tenant-specific secret webhook and CMS Max validates the provider resource host.
Tracking closure
CMS Max records tracking and updates shipped and fulfilled states once the matching shipment is accepted.
Implementation workflow
Accept the outbound order and inbound shipment together.
A valid API key proves authentication, not production readiness.
- 01
Prepare
Confirm API V2 access, carriers, warehouse, CMS Max stores, products, weights, shipping methods, queues, and support owners.
- 02
Configure
Activate the integration, save the encrypted API key, enable automatic sending, generate the webhook secret, and set origin and default weight.
- 03
Place
Create representative shipping orders and verify customer, address, item, amount, note, image, store, and package mapping.
- 04
Ship
Complete provider-side carrier and label operations, then trigger the accepted shipped-order event.
- 05
Reconcile
Verify tracking, CMS Max fulfillment state, duplicate protection, failures, customer notices, and manual recovery.
Practical reference
Protect the credentials and the callback URL.
The API key and secret-bearing webhook URL are operational secrets, not documentation values.
- Order source
- CMS Max ecommerce checkout and order record.
- Handoff scope
- Eligible shipping orders when automatic sync is active.
- Provider scope
- Shipment preparation, carriers, rates, labels, and warehouse operation.
- Return event
- SHIP_NOTIFY webhook followed by validated shipment retrieval.
- Final CMS Max state
- Tracking stored and order marked shipped and fulfilled.
Evidence and next steps
Use current product and primary-source guidance.
Features, provider requirements, plans, policies, interfaces, and search guidance can change. Verify the live CMS Max implementation and current official source before release.
Frequently asked questions
Make the practical decisions before launch.
Use each answer to identify configuration, evidence, testing, monitoring, and ownership.
Is ShipStation native to CMS Max?
Yes. The current CMS Max application includes the outbound shipment handoff and secured shipped-order webhook workflow.
Which orders are sent?
Only shipping fulfillment orders are eligible for the verified automatic path when the integration and settings are active.
Does CMS Max create carrier labels?
Not in the verified current integration. Carrier, rate, label, batch, manifest, and return operations remain in ShipStation.
How does tracking return?
ShipStation sends the shipped event to the protected webhook; CMS Max retrieves the shipment, matches the order, and records tracking.
What should happen if synchronization fails?
Monitor the queue and provider response, correct the cause, and retry only when duplicate behavior and order state are understood.
Connect direct checkout to an accountable fulfillment desk.
CMS Max can map the stores, products, order data, API access, webhook, test shipments, exception ownership, and customer communication needed for release.