Skip to content
WooCommerce

Shiprocket WooCommerce Integration: How It Works

Connecting a shipping aggregator to WooCommerce ends the copy-paste routine for every order. Here is how the connection usually works and what to check.

A customer paying by phone at a shop counter
9 sections · 7 min read
In this article · 9 sections

Orders are coming in, and every one of them means the same routine: copy the address from WooCommerce, paste it into a courier website, pick a service, print a label, then go back to WooCommerce, mark the order complete and send the customer a tracking number by hand. By the twentieth order of the day the copying mistakes start, and a parcel goes to the wrong pin code.

A Shiprocket WooCommerce integration is one common way Indian store owners get out of that loop. Shiprocket is a shipping aggregator: one account that gives you access to several courier companies, with labels, pickups and tracking in one panel. Connected to your store, it pulls orders in automatically and can send status back. This post explains how the connection generally works, what to prepare before you switch it on, and what to check when it does not behave. Features and screens change over time, so treat Shiprocket’s own help pages as the final word on the exact steps.

How the pieces fit together

It helps to picture the flow of one order:

  1. A customer places an order on your WooCommerce store and pays, or chooses cash on delivery.
  2. The order appears in your Shiprocket panel, with address, items, weight and payment method, pulled from the store.
  3. You (or a rule you set) choose a courier from the options available for that route and parcel.
  4. A shipping label and tracking number are generated, and a pickup is scheduled from your address.
  5. As the courier scans the parcel, the tracking status updates in Shiprocket and, depending on your settings, back on the order in WooCommerce.
  6. For cash on delivery parcels, the courier collects the money and it is passed back to you through the aggregator after delivery, on its remittance cycle.

WooCommerce stays the place where the order is created and the customer’s record lives. Shiprocket becomes the place where the parcel is handled. Keeping that split clear avoids a lot of confusion later about which system is “right”.

Before you connect shipping to WooCommerce

Most integration problems are really data problems that were already in the store. Sort these first.

Real weights and dimensions on every product

Couriers charge on the greater of actual weight and volumetric weight (a figure worked out from the box size). If your products have no weight, or a guessed one, rates shown at booking will be wrong, and the courier may later bill you for the difference. Set the store’s weight and dimension units in WooCommerce’s product settings, then fill in each product. For variations of different sizes, set the weight on each variation.

Clean addresses at checkout

Make the phone number and pin code required fields. Couriers call customers, and a wrong pin code can send a parcel down the wrong route or mark it undeliverable.

A pickup address and KYC done

Shiprocket asks for your pickup location and account verification before you can ship. Do this before go-live day.

Decide who pays for shipping, and how

The integration handles the parcel after the order. It does not, by itself, decide what the customer was charged at checkout. That still comes from your WooCommerce shipping settings or a shipping-rate plugin. If what customers pay and what couriers charge drift apart, our guide to shipping totals that look wrong at checkout walks through the usual causes.

Setting up a Shiprocket WooCommerce integration

The exact screens may differ, but the general shape of the connection is:

  1. Create and verify your Shiprocket account, including the pickup address.
  2. Add WooCommerce as a sales channel in the Shiprocket panel, entering your store’s address.
  3. Authorise access to the store. This typically uses WooCommerce REST API keys, which you create under WooCommerce’s advanced settings, or an approval screen in the store. Give the access the integration asks for, and note which WordPress user the keys belong to.
  4. Choose which order statuses to fetch. Usually orders that are paid and ready to ship (often “Processing”), not failed or pending ones.
  5. Check status sync settings, if offered, so that shipped and delivered updates reach WooCommerce.
  6. Place a test order and follow it all the way through before relying on it for real customers.

Aggregators often sell extra services on top of shipping. Treat each one as a separate decision; none of them is needed just to get orders flowing from the store to the courier.

Test it like a customer, then like a courier

A single test order is not enough. Run a few, each designed to catch a different problem:

  • A prepaid order with one simple product. Does it arrive in Shiprocket with the right weight and address?
  • A cash on delivery order. Is it marked as COD in the panel, with the right amount to collect? If you are still deciding how COD should work on your store, read our post on setting up COD on WooCommerce first.
  • An order with several items, including a variation. Is the total weight sensible?
  • An order to a remote pin code. Which couriers are offered, if any?
  • A cancelled order. Does it disappear from the shipping queue, or does someone still pack it?

Write down what happened with each. That note becomes your staff guide.

When orders do not sync, and other common problems

Orders are not appearing in Shiprocket

Check, in this order: that the order status matches the one the integration fetches; that the API keys still exist and belong to a user who still has the right role; that a security plugin or firewall is not blocking requests to the store’s REST API; and that the store address in the channel settings matches the live site, including https and www.

Status is not updating in WooCommerce

The sync back may be switched off, or may only update certain statuses. Also check whether another plugin changes order statuses on its own, which can overwrite updates.

Courier charges higher than expected

Most often the weight. Compare the weight on the product with what the courier recorded. Packaging adds both weight and volume.

Duplicate orders

This usually points to two connections to the same store, for example an old channel left active after reconnecting, or a plugin and a direct channel both running. Keep one.

Customers not getting tracking

Decide where tracking messages come from: Shiprocket’s notifications, WooCommerce emails, or a WhatsApp service. Sending from all three confuses customers. If WhatsApp is your main channel, our post on automatic WhatsApp order updates explains how those are usually wired up.

Cash on delivery money and reconciliation

With COD parcels, the cash goes from the customer to the courier, then through the aggregator to you. It does not arrive the moment the parcel is delivered. Shiprocket’s panel and agreement describe the current remittance schedule and any charges. Each week or fortnight, someone should match three lists: delivered COD orders in WooCommerce, remittances in the shipping panel, and money received in the bank. Returned parcels (often called RTO, return to origin) should be marked in WooCommerce too, so stock goes back and reports stay honest.

Is an aggregator the right choice for your store?

It suits many small and growing Indian stores because one account reaches several couriers, and you do not need separate contracts. It may suit you less if you ship mostly within one city with your own delivery staff, or if you already have a direct courier contract with good terms. Some stores use both: local orders delivered themselves, everything else through the aggregator.

Shipping choices also feed into what a store build includes. Courier integration and rate rules are one reason quotes for the cost of an ecommerce website in India vary so widely.

What to write down once it is connected

Keep a short record of how your Shiprocket WooCommerce integration was set up, so that anyone fixing it later starts from facts instead of guesses:

  • Which method connects the store (channel with API keys, or a plugin), and when it was set up.
  • The WordPress user the API keys belong to. If that person leaves and their account is deleted, the connection can stop.
  • Which order statuses are fetched and which are synced back.
  • Pickup addresses and which products ship from each.
  • Who has a login to the shipping panel and who receives its alerts.

It is a five-line note. It is also one of the first things a developer will need.

A short daily routine once it is running

  • Check that today’s paid orders all appear in the shipping panel.
  • Book couriers and print labels before the pickup cut-off.
  • Look at undelivered or exception parcels and contact those customers.
  • Glance at WooCommerce to confirm statuses moved as expected.

Ten quiet minutes a day catches the problems that otherwise surface as angry customer messages.

If your store is connected but orders are not syncing, statuses are wrong or weights are a mess, our WooCommerce support service can trace where the connection breaks and tidy the product data behind it. The aim is simple: an order placed on your site should reach the courier without anyone retyping an address.

Next in this series: Cash on Delivery in WooCommerce: Setup That Cuts Returns

Is Your Website Working Properly?

Get a free website health check from WebMaintor. We'll review your website's speed, security, forms, and technical health — and tell you exactly what needs attention.

No obligation. No automated reports. A real review by our team.