Click Post integration with Base: the step-by-step guide.
Prerequisites
-
Active ClickPost account with API login (username) and API key. (ClickPost authenticates via username+key across endpoints like label fetch.) If you don’t see it in your dashboard, ask your ClickPost CSM. Clickpost Implementation Guide
-
At least one courier partner mapped in your ClickPost account (e.g., Delhivery, Bluedart, Xpressbees, Ecom Express).
-
Complete shipper profile: legal name, pickup address, GSTIN, phone, and pincode. Carriers in India often require these for pickup creation. (Example: Delhivery mandates scheduled pickup requests.)
-
Optional but recommended in Base:
-
Add inventory weight/dimensions for products to improve rate accuracy.
-
Set COD & invoice preferences.
-
Connect ClickPost in the Base panel (with field-by-field help)
Path: Base dashboard → Integrations → +Add Integration
Couriers → ClickPost
Credentials
-
Account name: Any display name (e.g., “ClickPost – Delhi NCR”).
-
API login: Your ClickPost username.
-
API key: Your ClickPost key.
These power calls for order creation, AWB retrieval and labels.
Order identifiers & invoice
-
Reference no (dropdown): Choose the Base value that will become ClickPost’s
reference_number. Keep it stable; it’s used to fetch existing AWBs later if you regenerate. -
Full invoice number (dropdown): Map to your invoice field if your carrier requires it on the label for GST compliance.
Shipper (Sender) details
Fill contact person, company name, street, district, postal code, city, state, country exactly as registered with your carriers. Add Instructions for the courier if you routinely schedule pickups (e.g., entry gate, warehouse bay).
Parcel data automation
-
Get dimensions and weight from inventory: Tick to pull product master data; manual order weight (if present) takes priority (per the panel note).
-
Cardboard weight (packaging): Choose your method and enter a value (e.g., 0.10 kg / 100 g). This gets added per parcel to avoid under-declared weight surcharges.
Tip: If your lanes are volumetric-heavy (e.g., Mumbai → Guwahati), maintain accurate dimensions and a realistic packaging weight (100–250 g). It reduces re-weigh and RTO risk.
Click Save.
First label: create, download, print
-
Open an order in Base and choose Ship via ClickPost (from actions or bulk actions).
-
Base sends shipment data to ClickPost (Manifestation/Create Order). For India, ClickPost exposes a v3 endpoint for creating orders and returning label/AWB.
-
AWB is returned; label is generated (you can also fetch label later by AWB with username+key).
-
Print the PDF (4×6 / A6) on your thermal printer.
Need to re-download a label? Use “Fetch shipping label” (ClickPost API), or reprint from the order timeline.
Scheduling pickups & tracking shipments
-
Pickups: Many carriers require an explicit pickup request with slot/time. Create pickups per carrier SLA or let your carrier SPOC set daily schedules.
-
Tracking in Base: ClickPost standardizes statuses; use its tracking API + webhooks for near real-time updates that flow back into Base. (Think: out for delivery in Bengaluru, RTO initiated in Delhi, NDR reason captured.)
Best-practice settings
-
COD: Ensure “Payment method: COD” and “collectable amount” are mapped to ClickPost.
-
Pincode serviceability: If a lane fails, check carrier serviceability and COD limits for that pincode.
-
Dimensions units: Keep consistent (cm/kg) across Base and ClickPost.
-
Multiple warehouses: Create separate ClickPost accounts (or use distinct senders) per pickup city (Delhi NCR, Mumbai, Bengaluru, Hyderabad) for better SLA.
Troubleshooting (quick answers)
-
“Authentication failed” → Re-check API login & key; ensure the key hasn’t rotated. (ClickPost uses username/key on endpoints like label fetch.)
-
“Pincode not serviceable / COD not allowed” → Switch courier via rules or ClickPost’s recommendation API; some carriers restrict COD by pincode.
-
“AWB not generated” → Missing mandatory fields (phone, weight, dimensions) or invoice value; review Create Order v3 requirements for India.
-
“Label is blank / wrong size” → Re-fetch the shipping label via API; print at 100% scale (4×6).
-
“Pickup not happening” → Confirm daily pickup scheduling with carrier SPOC or create pickup requests with the carrier; some carriers won’t auto-dispatch without it.
Base + ClickPost
| Scenario | Base + ClickPost | Typical SME Aggregator (e.g., Shiprocket) | Single Carrier (e.g., Delhivery direct) |
|---|---|---|---|
| Scale & feature gating | Built for 3K–50K+ monthly shipments; enterprise flows. | Tuned for SMEs; pre-negotiated rates, simpler stack. | Great depth with that carrier; limited if you need multi-carrier. |
| Carrier coverage | 350+ integrations through a single API. | Wide India coverage but focused bundles; market consolidation (e.g., Pickrr acquisition). | Single network only |
| Routing logic | Recommendation API prioritizes courier by lane performance. | Basic rules/allocations vary by plan (vendor-claimed) | N/A |
| Tracking & events | Webhook + standardized events across carriers. | Tracking + notifications vary by plan/provider | Native to that carrier only |
For quick starts:
-
Get API login & key from ClickPost. Clickpost Implementation Guide
-
In Base: Settings → Integrations → Couriers → ClickPost
-
Fill Credentials:
-
Account name: Any display name (e.g., “ClickPost – Delhi NCR”).
-
API login: Your ClickPost username.
-
API key: Your ClickPost key.
These power calls for order creation, AWB retrieval and labels.
-
-
Choose Reference no, map Full invoice number.
-
Enter Sender address (with pincode/state).
-
Enable Get dimensions/weight from inventory; add Cardboard weight.
-
Save → open an order → Ship via ClickPost → print label.
-
Arrange pickup as per carrier. Delhivery API Integration
FAQ’s:
“Base ClickPost AWB not generated—what did I miss?”
Check that weight/dimensions, phone, invoice value and pickup address are present. If you retried, you can fetch the old AWB by reference number.
“Does ClickPost auto-pick the best courier for my lane?”
Yes—its Recommendation API ranks partners by historic performance (delivery time, delays, etc.). Use it in your routing rules.
“How do I print a 4×6 label?”
After shipping, click Download label (PDF) and print at 100% scale; re-fetch via the label API if needed.
“Can Base show live tracking from multiple couriers?”
Yes—ClickPost consolidates tracking and can push updates via webhooks; Base displays unified statuses (OFD, NDR, RTO, delivered).
“How do I schedule a pickup in Delhi NCR?”
Create a pickup request with your carrier (many require it) or ask your carrier SPOC to schedule daily pickups.
“Is COD supported?”
Yes. Map collectable amount when creating the order; carriers may restrict COD in some pincodes. Use routing/rules to switch carriers when COD is blocked.
Why use ClickPost with Base?
-
One connection, many couriers — ClickPost exposes a REST API layer with shipment creation, label, tracking and more, so you don’t integrate each carrier separately.
-
Enterprise scale + reliability — ClickPost emphasizes mid-to-large volumes (3K–50K+ shipments/month) with no feature gating. ClickPost
-
Better tracking & alerts — Webhooks and tracking APIs standardize statuses across 350–500+ carrier integrations.
-
Smart courier selection — A recommendation API suggests the best courier for a shipment based on historic performance and lane behavior. Postman