Create the fulfillment record
A queued order-placement listener sends eligible shipping orders to `/v2/shipments` when automatic synchronization is enabled.
Shipping operations / Native fulfillment integration
Connect CMS Max Orders to ShipStation Fulfillment
Move eligible shipping orders into the fulfillment workspace automatically, then return shipped status and tracking to the CMS Max order record.
The native CMS Max ShipStation plugin sends newly placed shipping orders to the ShipStation API when eCommerce, the plugin, credentials, and automatic sync are active. A secret-bearing shipped-order webhook returns shipment data, marks the CMS Max order fulfilled and shipped, and stores the tracking number.
- Automatic shipping-order handoff
- Encrypted API key and webhook secret
- Shipment status returned
- Tracking stored on the order
Fulfillment workflowCMS Max order to shipped status
Native two-way flow
Shipping operationsShipStation + CMS MaxNative fulfillment integration
Order sourceCMS Max
HandoffQueued API call
Return eventSHIP_NOTIFY
Final stateShipped + fulfilled
01Shipping order is placedCMS Max evaluates plugin and sync settings
02Shipment is createdOrder, address, item, and amount data is sent
03Team ships the orderShipStation owns carrier and label operations
04Webhook returns statusCMS Max stores tracking and closes fulfillment
What the integration does
A native handoff from owned checkout to shipping operations.
CMS Max maps a shipping order into a ShipStation V2 shipment with an external order number, customer and store addresses, item SKUs and quantities, order amounts, package weight, and a sales-order flag. The integration does not quote carriers or create labels inside CMS Max; ShipStation remains the fulfillment workspace for those provider capabilities.
Operate in ShipStation
Use the provider account for shipment preparation, carrier services, rates, labels, batches, manifests, returns, and other available fulfillment tools.
Close the CMS Max order
A secured `SHIP_NOTIFY` webhook fetches the provider shipment, matches the CMS Max order number, records tracking, and marks the order shipped and fulfilled.
Operating boundary
Keep checkout, shipment preparation, and final order status aligned.
The two-way connection is strongest when each system has a clear source-of-truth role and exceptions have a documented recovery path.
| Area | Primary owner | Supported contract |
|---|---|---|
| Catalog, checkout, and order record | CMS Max | Owns products, cart, customer order, payment state, fulfillment choice, order totals, addresses, and customer-facing order history. |
| Shipment creation payload | CMS Max integration | Sends shipping orders with external number, addresses, items, amounts, store origin, and default package weight. |
| Carrier, rate, and label operations | ShipStation | Owns the provider-side shipment workflow and any carriers, services, labels, batches, manifests, returns, and account billing used there. |
| Shipped-order notification | ShipStation to CMS Max | Posts the resource URL and event type to the tenant-specific secret webhook so CMS Max can retrieve shipment details. |
| Exceptions and reconciliation | Fulfillment team | Owns failed sends, duplicate records, bad addresses, missing weights, unmatched order numbers, delayed webhooks, voids, and support response. |
Connected workflow
Send only eligible orders and close them only after the shipping event.
The code intentionally limits automatic handoff to orders whose fulfillment method is `shipping`; pickup and local-delivery orders stay out of ShipStation.
Configure
Activate CMS Max eCommerce and ShipStation, enter the encrypted API key, enable automatic order sending, save to generate the webhook secret, and set store origin and default weight.
Place
When a shipping order is placed, the queued listener builds customer, address, item, price, tax, shipping, note, store, and package data.
Create
CMS Max posts the shipment with the order number as its external ID and asks ShipStation to create the associated sales-order context.
Ship
The fulfillment team chooses the provider-side carrier, service, package, label, batch, and operational process available in the ShipStation account.
Return
The secured shipped-order webhook fetches shipment details, finds the CMS Max order, records tracking, and updates shipped and fulfilled states once.
High-value applications
Connect direct ecommerce demand to a dedicated shipping desk.
The integration reduces re-entry while keeping the CMS Max storefront and order record connected to the provider fulfillment process.
Daily shipping queue
Send eligible paid or placed shipping orders into the fulfillment workspace as they enter the CMS Max order lifecycle.
Multi-item orders
Transfer item names, SKUs, quantities, unit prices, and available product imagery with the customer and order context.
Store-origin fulfillment
Use the configured CMS Max store shipping origin as the provider shipment `ship_from` address.
Tracking completion
Return the shipped event and tracking number to the CMS Max order so staff and customer-facing workflows see the final fulfillment state.
Governance and trust
Protect API credentials and treat the webhook URL like a password.
The integration stores the API key and webhook secret encrypted, validates the tenant and secret, and restricts provider resource URLs before retrieving shipment data.
Credential security
Keep the API key and secret-bearing webhook URL out of page content, tickets, screenshots, analytics, repositories, and public documentation.
Provider URL validation
CMS Max accepts only shipment resource hosts ending in `shipstation.com`; monitor and reject unexpected or malformed callback data.
Data minimization
Review customer email, addresses, phone, order notes, items, prices, tax, shipping, and image URLs sent to the fulfillment provider.
Queue and retry operations
Monitor failed order sends and webhook jobs, provider authorization errors, rate limits, malformed responses, duplicate events, and manual recovery.
Search and conversion continuity
Protect the post-purchase experience created by strong product discovery.
ShipStation does not create search visibility directly. It helps the business fulfill the orders earned by CMS Max product, category, content, local, campaign, and direct checkout experiences.
Clear shipping policy
Publish useful delivery estimates, processing windows, destinations, carrier expectations, tracking support, returns, and holiday deadlines in CMS Max.
Accurate product data
Maintain SKUs, titles, images, dimensions, weights, availability, and fulfillment restrictions so downstream operations receive dependable records.
Order confidence
Keep transactional notices, order history, tracking, customer support, and exception communication connected to the owned CMS Max experience.
Operational feedback
Use fulfillment errors, address corrections, packaging issues, returns, and support cases to improve product and checkout content.
Implementation sequence
Accept order creation, provider fulfillment, and the shipped callback together.
A working API key proves only authentication. The production acceptance plan must cover real order data, fulfillment operations, webhook security, and recovery states.
Prepare
Confirm the ShipStation plan and V2 API access, carrier and warehouse setup, CMS Max stores, products, weights, shipping methods, orders, queues, and support owners.
Configure
Activate the plugins, save the encrypted key, choose automatic sending, generate the webhook secret, add the exact CMS Max URL to the ShipStation shipped-order event, and protect it.
Accept
Test shipping versus pickup orders, addresses, country normalization, missing weights, multi-item orders, amounts, duplicate sends, provider errors, labels, tracking, and webhook authentication.
Release
Monitor initial shipments, queue failures, API responses, unmatched orders, webhook latency, duplicate events, tracking quality, fulfillment status, and customer support.
Implementation references
Review the platform and provider evidence.
Provider products and requirements change. These references support discovery; the production implementation and acceptance evidence remain authoritative for each CMS Max site.
ShipStation FAQ
Questions teams ask before they connect.
Final scope depends on account configuration, customer journeys, data policy, connected systems, operational ownership, and acceptance criteria.
Is ShipStation a native CMS Max integration?
Yes. CMS Max includes encrypted settings, a queued shipping-order listener, ShipStation V2 API client and data mapping, a secret-bearing webhook endpoint, queued shipment processing, tracking storage, and shipped-order fulfillment updates.
Which CMS Max orders are sent?
Only orders whose fulfillment method ID is `shipping` are sent, and only when CMS Max eCommerce and ShipStation are active, automatic sending is enabled, and an API key is configured. Pickup and local-delivery orders are excluded.
What order data is sent?
The integration sends the order number, customer email, billing and shipping addresses, item names, SKUs, quantities, unit prices, available image URL, amount paid, shipping, tax, notes, store origin, and package weight.
Does CMS Max create labels through ShipStation?
Not in the verified current integration. CMS Max creates the provider shipment and sales-order context; carrier selection, rates, labels, batches, manifests, returns, and related fulfillment work remain in ShipStation.
How does shipped status return to CMS Max?
ShipStation posts a `SHIP_NOTIFY` payload to the tenant-specific secret webhook. CMS Max fetches the shipment from the validated provider URL, matches the order number, records tracking, and marks the order shipped and fulfilled.
How are the API key and webhook protected?
Both values are encrypted in CMS Max settings. The webhook verifies the tenant and secret, and the follow-up resource URL must use a host ending in `shipstation.com`. Treat the generated webhook URL like a password.
Connect with confidence
Connect the owned checkout to a controlled shipping workflow.
Bring the ShipStation account and API access, carriers, warehouses, CMS Max stores, shipping methods, product SKUs and weights, order volume, fulfillment team, webhook owner, customer notices, error procedures, test orders, and launch measures. CMS Max will configure and accept the two-way flow.
ShipStation is a trademark of its respective owner. CMS Max scope is described on this page and may differ from the provider's complete product offering.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.