Accurate inputs create useful quotes
Maintain the shipping origin, destination, product weight, dimensions, parcel rules, and service configuration used to request a FedEx rate.
FedEx carrier integration
Connect eligible FedEx services to checkout without building a carrier stack from scratch.
CMS Max uses its Shippo integration to request eligible FedEx rates for packed parcels, present allowed services at checkout, and support downstream label and tracking workflows. Your carrier account, service eligibility, package data, and operating process still determine the real result.

Shipping architecture
Connect account access to accurate catalog data, parcel preparation, checkout policy, fulfillment ownership, customer communication, and financial reconciliation.
Maintain the shipping origin, destination, product weight, dimensions, parcel rules, and service configuration used to request a FedEx rate.
Checkout quotes can include account-specific pricing when available, but carrier adjustments, surcharges, packaging, pickup, and shipment details can change final billed cost.
Assign owners for account access, checkout testing, label purchase, exceptions, tracking, billing review, and customer communication.
CMS Max shipping capabilities
Availability depends on active plugins, account mode, connected and eligible carrier services, current provider support, accurate data, origin, destination, parcel, and tenant configuration.
Connect an eligible FedEx carrier account in Shippo or use an available Shippo-supported carrier account, subject to current account, region, and verification requirements.
CMS Max sends packed parcel and address information to Shippo, receives available carrier rates, and can present allowed FedEx service levels to the shopper.
CMS Max packs shippable cart items into parcel requests so rates reflect the number, dimensions, and weight of boxes instead of simply treating every product as a separate shipment.
Restrict checkout options to selected carriers and service levels so customers see the FedEx choices the business is prepared to fulfill.
The Shippo-backed workflow supports label purchase, supported label formats, refund requests for eligible unused labels, and carrier tracking data tied to fulfillment operations.
A configured flat fallback rate can preserve a checkout option during qualifying carrier-service failures, while Shippo API logs help administrators investigate requests and errors.
Order-to-delivery flow
Each stage needs valid inputs, observable results, an exception path, and a named owner.
Store accurate weights, dimensions, and shipping eligibility.
Build parcel data for the shippable cart.
Request eligible FedEx services through Shippo.
Present allowed options and record the choice.
Purchase the label, ship, track, and reconcile.
Implementation sequence
Move from account ownership to checkout and warehouse testing before making a shipping promise public.
Document destinations, package profiles, service levels, handling times, cutoff times, exclusions, returns, and customer-facing expectations.
Confirm the intended account, billing relationship, authorized users, carrier verification, negotiated-rate expectations, and supported services.
Set the store origin and maintain product weights, dimensions, shipping zones, methods, package rules, and any carrier or service filters.
Activate Shippo, connect FedEx, verify available services, and test realistic residential, commercial, nearby, distant, heavy, oversize, and invalid-address cases.
Purchase representative labels, verify print format, confirm tracking, test an eligible refund path, and document void, pickup, exception, and support procedures.
Compare checkout charges with carrier invoices, review adjustments and fallback usage, investigate API errors, and measure delivery and support outcomes.
Operational ownership
CMS Max, Shippo, the carrier, and the merchant each own different parts of the workflow. Clear boundaries make support and recovery faster.
Documentation and related resources
Provider interfaces, terms, services, formats, and regional availability can change. Use official documentation and production tests during implementation.
Shipping integration FAQ
Turn each answer into configured rules, representative tests, monitoring, and written ownership.
The current CMS Max shipping architecture connects FedEx as a carrier through the Shippo plugin. Shippo supplies the multi-carrier API layer used for eligible rates, labels, and tracking workflows.
Yes, when Shippo is active, an eligible FedEx carrier account and services are available, the destination is supported, and the store provides the parcel and address data required for rating.
No. A carrier quote is an estimate based on submitted data. Final charges can differ because of measured weight or dimensions, address corrections, fuel and residential surcharges, special services, pickup, and other carrier adjustments.
Yes. CMS Max Shippo settings support allowed-carrier and allowed-service-level filters. Availability still depends on the connected account, parcel, origin, destination, and carrier response.
The Shippo-backed CMS Max workflow supports label operations and tracking data for eligible carrier services. Exact capabilities and formats depend on current Shippo and FedEx support and account configuration.
A CMS Max shipping method can use a configured flat fallback rate for qualifying Shippo failures. The merchant should choose that amount deliberately, monitor its use, and define when fulfillment staff must contact the customer.
Ship with confidence
Bring your carrier accounts, package profiles, destinations, service promises, label workflow, exception policy, and cost targets. CMS Max will help map the supported implementation.
The world's fastest and most SEO friendly website code.