Use the current connection model
CMS Max connects UPS through Shippo. Merchant users of a third-party platform generally connect the relevant UPS account rather than creating a separate direct UPS API application.
UPS carrier integration
Bring eligible UPS services into checkout and keep fulfillment connected to the order.
CMS Max connects eligible UPS carrier services through Shippo, using address and packed parcel data to request checkout rates and support label and tracking workflows. The result is a maintainable shipping operation rather than a legacy UPS Developer Kit project embedded in the storefront.

Shipping architecture
Connect account access to accurate catalog data, parcel preparation, checkout policy, fulfillment ownership, customer communication, and financial reconciliation.
CMS Max connects UPS through Shippo. Merchant users of a third-party platform generally connect the relevant UPS account rather than creating a separate direct UPS API application.
Accurate dimensions, weight, addresses, package count, service selection, and additional services are essential to meaningful rating and billing reconciliation.
Labels, pickup or tendering, tracking exceptions, address corrections, claims, returns, invoices, and customer communication require named operators.
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.
Activate an available Shippo UPS account or connect an eligible merchant UPS account, complete current terms and account requirements, and verify the billing relationship.
CMS Max prepares address and packed parcel data, Shippo requests eligible UPS rates, and the storefront can present the allowed returned services.
The shipping system groups shippable products into parcel requests within configured constraints, helping rates reflect actual boxes instead of a raw item count.
Limit results to UPS and the service levels the business intends to offer, while respecting account, parcel, origin, destination, and carrier eligibility.
Use supported Shippo transaction workflows for eligible UPS labels and normalized tracking data, with output formats selected for the fulfillment workstation.
Use a deliberate flat fallback for qualifying rating failures and review Shippo API logs, order details, and carrier records when troubleshooting discrepancies.
Order-to-delivery flow
Each stage needs valid inputs, observable results, an exception path, and a named owner.
Maintain accurate products, addresses, zones, and parcels.
Link eligible UPS carrier access through Shippo.
Request eligible UPS services for the packed cart.
Record the customer selection and create the label.
Tender, track, support exceptions, and reconcile billing.
Implementation sequence
Move from account ownership to checkout and warehouse testing before making a shipping promise public.
List destinations, package types, service levels, negotiated-rate expectations, cutoff and handling times, returns, pickups, and customer promises.
Confirm the UPS profile, shipper account numbers, authorized users, current Shippo connection path, terms acceptance, and billing responsibility.
Set store origin, product weights and dimensions, zones, methods, parcel behavior, allowed carrier and service filters, label format, and fallback rate.
Activate or add UPS in Shippo, then confirm eligible services and rates for representative origins, destinations, parcel types, and address quality.
Create labels, verify print dimensions, confirm tracking, document pickup or drop-off, test an eligible void or refund, and train exception owners.
Compare checkout shipping revenue with UPS charges, review dimensions and adjustments, monitor fallback use, investigate delivery exceptions, and refine rules.
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 UPS as a carrier through Shippo. The page no longer instructs merchants to build against the legacy Developer Kit as a separate storefront project.
UPS states that customers using third-party applications generally do not need their own API credentials. The relevant UPS account must still be associated, eligible, and connected through the current Shippo workflow.
Eligible account-specific pricing may be returned when the connected UPS and Shippo account relationship supports it. Verify with representative shipments and reconcile against actual UPS invoices.
Yes. CMS Max Shippo settings support allowed-carrier and service-level filters. Returned options still depend on the account, origin, destination, parcel, and current carrier response.
The Shippo-backed workflow supports eligible carrier label operations and normalized tracking data. Confirm the exact services, label formats, account requirements, and production behavior during testing.
Carrier invoices can reflect measured dimensions or weight, address corrections, residential and fuel surcharges, additional handling, pickup, service changes, and other adjustments not present in the original request.
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.