Aras Kargo Shopify Integration: Rates vs Fulfillment

First decide: checkout rates, post-purchase fulfillment, or both

Start by identifying the moment your shipping process needs to connect to Shopify. Carrier-calculated shipping (CCS) means Shopify requests live rates from connected carrier accounts during checkout and shows the available options to the customer.

That distinction matters because a checkout rate answers, “What should this customer pay for shipping?” A fulfillment workflow answers, “How does the shipment get processed after the order is placed, and how does Shopify learn what happened?” One integration may not cover both questions. Write down which stages need automation before choosing a solution.

If you need customers to see Aras Kargo rates before paying, investigate a checkout-rate path. If your main need is to send orders for shipment, create labels, or return tracking after purchase, focus on fulfillment. If you need both, assess the two workflows independently and confirm whether the implementation can support both without assuming that one capability includes the other.

If the need is checkout pricing, assess Shopify CCS

For checkout pricing, CCS bases live shipping options on an order’s weight, dimensions, and destination. Treat the quality of the input data as part of the integration plan: review product weights, measure packed products, and test representative baskets and destinations before relying on the displayed rates.

Shopify uses the smallest saved box that fits a shipment to estimate rates when products have packed product sizes saved. That makes packaging data worth checking before you investigate rate discrepancies. If estimates look wrong, compare the products’ saved packed sizes and the resulting shipment assumptions with the way orders are actually packed.

Shopify lists CCS as available on Advanced and Plus, with an additional option for Grow stores. A Grow store can add CCS for an additional monthly fee or by switching to annual billing. Confirm the store’s current plan and eligibility as an early implementation check, rather than designing around a checkout-rate feature before verifying access.

Plan for what shoppers see when calculated rates are unavailable. A backup rate appears only if calculated rates fail and no other eligible rate is available. Eligible flat rates can still appear alongside working calculated rates, so a customer may choose a flat rate instead. Review the full set of eligible checkout options; otherwise, a rate test can pass while the actual checkout presents a different choice.

For post-purchase processing, compare Shopify’s fulfillment models

For post-purchase processing, choose between an email-based custom fulfillment service and an app-integrated fulfillment service based on how much coordination Shopify needs to handle. A custom fulfillment service is suitable when the fulfillment provider can process orders by email. Activating one creates a fulfillment location in Shopify where products can be stocked.

With this model, assigning products to the service and marking an order fulfilled in Shopify admin sends the service an email with order details. It can be a reasonable fit when the handoff is simple and your team is comfortable tracking progress with the service directly.

If the service needs more than email to process orders, Shopify points merchants to a custom app integration. An app-integrated fulfillment service lets merchants manage requests, progress, communication, and cancellations from Shopify admin. Fulfillment status updates automatically as the service processes orders.

Choose the app path when you need a connected workflow rather than a message handoff, but map the work before committing to it. List what information must go out with a request, what status changes need to come back, and who handles exceptions.

Map products, orders, and tracking before implementation

Map the fulfillment method at the product level, then test orders that combine different products. Shopify’s fulfillment method is selected per product, so one order can use different fulfillment methods for different items. That means a single customer order may need more than one operational handoff; agree in advance how your team will see and manage that split.

For an email-based custom service, define who checks the provider’s progress and who updates Shopify when the shipment is sent. After the service ships an order, merchants can manually add tracking information to Shopify so customers can track the shipment. Include that manual step in the operating procedure, and decide how the team will check that tracking is present and correct.

For an app-integrated service, establish what the service returns and how staff should handle missing or incorrect information. When a fulfillment app provides tracking information, Shopify adds it to the order automatically; merchants can also add or update tracking manually. Test both the normal automated path and the correction path, rather than treating automatic updates as a reason to skip monitoring.

Keep checkout pricing and shipment execution in separate test cases. A rate that appears correctly before purchase does not demonstrate that a fulfillment request, shipment update, or tracking handoff works after purchase. Verify each stage using the order types and product combinations your store expects to process.

Check the app workflow’s request and cancellation boundaries

An app-based fulfillment request changes what staff can safely do with an order, so design the order-editing process around the request step. After an app-integrated fulfillment request is sent, its status becomes In progress while the service responds.

Shopify’s app-fulfillment workflow has a post-request editing boundary: an order can’t be edited or refunded after a fulfillment request is made. Decide who checks order details before requesting fulfillment, and make that check part of the handoff rather than an informal reminder. This is especially important when product, address, or quantity changes are common in your operation.

Cancellation also depends on whether the service has accepted the request. If it has not yet been accepted, the request can be canceled directly in Shopify admin. Document who owns that follow-up and how the team will handle an order while the response is pending.

Confirm Aras Kargo requirements, then choose the integration path

Before selecting an implementation, confirm directly with Aras Kargo whether API access is available to your business and which services and shipping workflows that access supports. Ask specifically about the capabilities your design depends on, such as obtaining checkout rates, submitting shipment details, creating labels, receiving tracking information, or handling changes and cancellations. Treat each capability as unconfirmed until Aras Kargo verifies it.

Then map the confirmed requirements to Shopify’s workflow boundaries. If the requirement is live checkout pricing, assess CCS and verify plan eligibility, rate inputs, and the checkout options customers may see. If the requirement is post-purchase processing that can run by email, assess the custom fulfillment service and include manual status and tracking work in the process. If the service requires more than email or you need fulfillment management in Shopify admin, evaluate a custom app integration.

If both checkout pricing and fulfillment are needed, keep them as distinct acceptance checks even if you pursue a connected implementation. Agree on what a successful test looks like for rate display, order handoff, fulfillment status, and tracking before development begins. This gives your team a way to compare implementation options against confirmed Aras Kargo capabilities without assuming that Shopify or the carrier provides an unsupported feature.