Delhivery shipping for GoCommerce

What it does

Configuration

Three settings are required: the API token, the pickup warehouse’s nickname and the seller name. Set them in Config from your own main(), or leave Config empty and fill them in under Settings › Shipping providers.

The module reads its Config struct, not the environment. The variable names are the ones the package’s own example or the reference binary uses; in your own main() you choose where each value comes from. Where a setting has a panel label, the admin’s settings drawer can hold it too, and a value typed there wins over Config.

Setting it up

1. Register the warehouseIn Delhivery, register the pickup warehouse and note its nickname exactly — it is matched case-sensitively — and copy the API token.
2. Install the moduleImport it and pass delhivery.New to gocommerce.New, as below — or run the reference binary with -carriers, which installs every carrier module idle.
3. Configure itToken, pickup location and seller name, in Config or under Settings › Shipping providers. Add the GSTIN and HSN code if your goods need them.
4. Ship an orderChoose Delhivery in the admin’s ship dialog, or POST /api/admin/create-fulfillment with "provider": "delhivery". The waybill becomes the tracking number.

import (
	"os"

	"github.com/itswadesh/gocommerce/core"
	delhivery "github.com/itswadesh/gocommerce/ext/fulfill-delhivery"
)

app, err := gocommerce.New(cfg,
	delhivery.New(delhivery.Config{
		Token:          os.Getenv("DELHIVERY_TOKEN"),
		PickupLocation: "Primary",
		SellerName:     "Acme Retail",
	}),
)

How it works

• A form with JSON inside

  The manifest is posted to /api/cmu/create.json as a URL-encoded form, format=json and data= holding the payload — the shape that endpoint accepts.

• A refusal is a failure

  Delhivery can answer 200 with a refusal inside. A package without a waybill is treated as refused and Delhivery’s remarks are returned, so the engine does not move the order to shipped.

• COD is this parcel’s value

  An unpaid order is booked COD with cod_amount set to the value of what is in this parcel; a paid order is booked Prepaid and collects nothing.

• Grams and centimetres

  Weight goes in grams and the sides in centimetres, kept to the tenth. The engine’s measured weight is used only when every line was weighed; otherwise the default per unit.

• A new id per parcel

  Delhivery rejects a duplicate order id, so the first parcel goes as the order number and later ones as number-2, number-3 and so on.

• Pre-pulled waybills

  A waybill passed in the request’s meta is sent with the manifest — in the code’s words, how a store prints labels ahead of manifesting them.

What it does not do

Read these before an order depends on it. No store is known to run GoCommerce in production yet, so these come from the code, not from anyone’s experience.

• No label URLThe module returns the waybill and the carrier, not a label. Labels come from Delhivery’s own tools.
• No tracking updatesNothing comes back after manifesting: no webhook, no polling. Marking an order delivered is a separate step, in the admin or through the API.
• No rates, pickups or cancellationIt quotes no rates and books no pickup, and deleting a fulfillment in GoCommerce does not cancel the manifest in Delhivery.
• The units are an assumptionThe package doc says Delhivery’s documentation does not state its units; grams and centimetres are what working integrations send. A store that finds otherwise should say so.
• One HSN code for the storeHSNCode is a single setting sent with every parcel. A catalogue with goods under several codes cannot vary it per product.
• Rupees only, in practiceAmounts are minor units divided by 100. The code notes that is exact for INR, the only currency Delhivery settles cash on delivery in.