Treat shipping as a system
Origin, destination, zones, products, packing, rates, checkout, orders, labels, tracking, returns, support, and billing need one documented operating model.
Multi-carrier shipping platform
Shippo Shipping for CMS Max
Run multi-carrier checkout and fulfillment from one connected commerce workflow.
The CMS Max Shippo plugin connects checkout rating, parcel data, address validation, carrier and service filters, label creation, tracking, refunds, and API visibility. Choose a CMS Max managed account path or connect your own Shippo credentials, then operate the full shipping lifecycle with clear ownership.
- Multi-carrier rates
- Address validation
- Label formats
- Tracking
- API logs
with CMS Max
01Choose account mode
02Configure carriers
03Operate shipping
Shipping architecture
A reliable shipping promise starts before the rate request.
Connect account access to accurate catalog data, parcel preparation, checkout policy, fulfillment ownership, customer communication, and financial reconciliation.
Control what customers can choose
Connect the right carrier accounts, then limit carriers and service levels to options the business can actually prepare, tender, support, and reconcile.
Design for service interruptions
Use representative tests, API logs, a deliberate fallback rate, alerting, and a manual recovery process so a provider issue does not become a silent checkout failure.
CMS Max shipping capabilities
From a shippable cart to an operated delivery workflow.
Availability depends on active plugins, account mode, connected and eligible carrier services, current provider support, accurate data, origin, destination, parcel, and tenant configuration.
Managed or merchant-owned access
Use the CMS Max Enterprise managed-account path where available or connect a custom Shippo API key for an account the merchant controls directly.
Multi-carrier rate requests
CMS Max sends the ship-from and ship-to addresses plus packed parcel data to Shippo and combines eligible returned rates with the store shipping configuration.
Address checks
The integration supports Shippo address validation so checkout can identify or suggest corrections for supported address issues before fulfillment.
Carrier and service-level filters
Choose allowed carriers and allowed service levels, leaving a filter empty only when all currently connected and eligible options should be considered.
Fulfillment file formats
Purchase eligible labels and use the configured PDF, PDF 4x6, PNG, or ZPLII output that matches the team and printer workflow.
Tracking, refunds, logs, and fallback
Support carrier tracking data, eligible unused-label refund requests, administrator API logs, and a configured flat checkout fallback for qualifying service failures.
Order-to-delivery flow
Keep the customer choice connected to fulfillment.
Each stage needs valid inputs, observable results, an exception path, and a named owner.
Configure
Set account mode, origin, carriers, services, and formats.
Validate
Check customer address and shipping eligibility.
Pack
Convert shippable products into parcel requests.
Rate
Return eligible carrier choices to checkout.
Fulfill
Buy labels, track, handle exceptions, and reconcile.
Implementation sequence
Test the real packages and real operating conditions.
Move from account ownership to checkout and warehouse testing before making a shipping promise public.
01. Map the shipping operation
Document products, parcel types, destinations, service promises, carrier relationships, negotiated rates, label printers, returns, and support ownership.
02. Select the account path
Choose the CMS Max Enterprise managed option when provisioned or use a merchant-owned Shippo account and protected API key.
03. Connect carriers
Provision the managed account or add supported carrier accounts in Shippo, complete carrier-specific terms or verification, and confirm billing ownership.
04. Configure commerce inputs
Maintain the store origin, product weights and dimensions, zones, methods, carrier filters, service filters, label format, and a deliberate fallback rate.
05. Run end-to-end tests
Test address correction, rate results, mixed carts, multiple parcels, filters, fallback behavior, label purchase, print output, tracking, and an eligible label refund.
06. Operate and improve
Review API errors, carrier invoices, shipping-margin variance, delivery exceptions, fallback usage, refunds, customer contacts, and configuration changes.
Operational ownership
Know which system controls each outcome.
CMS Max, Shippo, the carrier, and the merchant each own different parts of the workflow. Clear boundaries make support and recovery faster.
- CMS Max
- Owns the store configuration and commerce workflow that prepares requests, presents shipping options, records the order, and supports administrators.
- Shippo
- Owns the current multi-carrier API platform, carrier-account connection model, normalized rate and tracking responses, and supported transaction operations.
- Carriers
- Control services, account eligibility, acceptance, actual transportation, adjustments, delivery events, claims, restrictions, and network availability.
- Merchant
- Owns accurate data, connected accounts, packaging, promises, tendering, credential access, labels, customer service, billing reconciliation, and exceptions.
Documentation and related resources
Confirm current account and carrier requirements.
Provider interfaces, terms, services, formats, and regional availability can change. Use official documentation and production tests during implementation.
Shipping integration FAQ
Resolve the operational questions before launch.
Turn each answer into configured rules, representative tests, monitoring, and written ownership.
What does the CMS Max Shippo plugin do?
It connects CMS Max to Shippo for supported multi-carrier rate requests, address validation, carrier and service filtering, labels, tracking data, eligible refunds, API logs, and checkout fallback handling.
Do I need my own Shippo account?
Not always. CMS Max supports an Enterprise managed-account path when provisioned and a custom-account path for merchants who want to use their own Shippo credentials and carrier relationships.
Which carriers can I use?
Carrier availability depends on Shippo support, the account mode, connected carrier accounts, region, origin, destination, parcel, services, terms, and verification. CMS Max can filter the connected carriers and service levels offered at checkout.
What product information is needed for useful rates?
Maintain accurate shipping eligibility, weight, dimensions, quantity, origin, destination, and applicable package rules. Incomplete or inaccurate inputs can produce unavailable or misleading quotes and later carrier adjustments.
Which shipping label formats are supported?
The current CMS Max setting supports PDF, PDF 4x6, PNG, and ZPLII. Actual carrier and service support should be confirmed with a representative production test.
Can Shippo prevent checkout failure during an outage?
CMS Max can apply a configured flat fallback rate for qualifying Shippo API failures. It is a continuity tool, not a live quote, so the merchant should set it carefully and monitor every use.
Ship with confidence
Build checkout and fulfillment as one operating system.
Bring your carrier accounts, package profiles, destinations, service promises, label workflow, exception policy, and cost targets. CMS Max will help map the supported implementation.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.