Skip to content
KanchanFlow
IntegrationBuilding· Wave 2 · Q2 2027Last tested 2026-08-27Logistics

FedEx for Manufacturing

Label creation, rating and tracking for USA domestic and export shipments. In development, targeted at Wave 2 Q2 2027.

In short

KanchanFlow, the RFQ-to-Order CRM, is building a FedEx connector for label creation, rating and tracking on USA domestic and export shipments, including the commercial invoice data an international consignment needs. It is a Wave 2 item with a Q2 2027 target and is the furthest out of anything in our catalogue.

Diagram of the FedEx integration: fields KanchanFlow writes to FedEx on the left, fields it reads back on the right.

FedEx is the connector USA manufacturers ask for most often and it is the one furthest from shipping, which is an uncomfortable thing to write on a page whose purpose is to sell software. We are writing it anyway, because a roadmap that hides its own gaps is worthless.

When it ships, it will create labels from the dispatched order, rate a shipment before it is quoted, track it to delivery and carry the commercial invoice data an export consignment needs. Until then, the honest answer is that you will keep using FedEx Ship Manager, and this page will say so.

Status
Building · Wave 2 · Q2 2027
Category
Logistics
Plan availability
Professional and Enterprise (planned)
Sync cadence
Planned: real time tracking updates by subscription, with a 30-minute reconciliation poll

Field by field

What syncs, in both directions

These are the actual fields that move. Anything not on these two tables does not sync, and we would rather write that down than let you assume it does.

KanchanFlow → FedEx

What we write out when a record moves forward.

FieldWhat we send
Label creationPlanned: recipient details, package dimensions and weight, service level and payment terms, submitted to generate a shipping label for the dispatched order.
Rate requestPlanned: a rating call before dispatch, and optionally at quoting time, so freight on a quote reflects a real rate rather than an estimate somebody remembered.
Commercial invoice dataPlanned: harmonised codes, country of origin, declared value and incoterms for international consignments, which is where most export shipping errors actually originate.
Pickup requestPlanned: pickup scheduling against your registered account and location.
Third-party and recipient billingPlanned: shipping billed to the customer's own FedEx account, which is how a large share of manufacturing freight is actually paid for.

FedEx → KanchanFlow

What comes back onto the customer, quote or order record.

FieldWhat we read
Tracking number and labelPlanned: the tracking number and the printable label attached to the order.
Rate quotesPlanned: service options with cost and transit time, so a dispatcher can choose knowingly rather than defaulting to overnight.
Tracking milestonesPlanned: every scan through to delivery, on the customer timeline.
Delivery confirmation and signaturePlanned: delivery confirmation and, where the service includes it, the signature image.
Exception eventsPlanned: delivery exceptions, customs holds and address corrections, raised as tasks.

Sync cadence. Planned: real time tracking updates by subscription, with a 30-minute reconciliation poll. Every record also carries a Sync now control, and the last successful sync time is shown on the record so nobody works from a number of unknown age.

Figures

What this looks like in the product

We do not ship stock imagery or mocked-up screens. These three figures describe the exact shots a designer must capture from a live workspace, each carrying a visible date stamp and recaptured at every quarterly re-test.

Figure 1 · to be captured
The dispatch panel with FedEx service options, rates and transit times returned for a real shipment.

Capture date required. Cannot be captured until release; this connector is targeted at Wave 2 Q2 2027. Do not publish a mockup.

Figure 2 · to be captured
A generated FedEx label attached to the order record with the tracking number visible.

Capture date required. Capture at release with recipient details masked. Date stamp required.

Figure 3 · to be captured
An international consignment showing commercial invoice fields including harmonised codes and incoterms.

Capture date required. Capture at release from a genuine export shipment. Date stamp required.

10 steps

Setting it up

Written for the person who will actually do it, in the order they will do it. Nothing here assumes you have done this before.

  1. 1Planned: obtain a FedEx developer account and register an application for production API access.
  2. 2Planned: link your FedEx shipping account number and complete FedEx's production certification, which is a review process rather than an instant approval.
  3. 3Planned: in KanchanFlow, open Settings, Integrations, FedEx and enter the API credentials and account number.
  4. 4Planned: map ship-from locations to the CRM plants that dispatch from them.
  5. 5Planned: configure default service levels and package types per product line.
  6. 6Planned: set up billing rules, including third-party and recipient billing for customers who ship on their own account.
  7. 7Planned: configure the commercial invoice defaults for exports, including your default incoterms and country of origin.
  8. 8Planned: set harmonised codes on your item master, because an export label without them will fail at customs, not at the connector.
  9. 9Planned: restrict label creation to the dispatch role.
  10. 10Planned: run test labels in the FedEx sandbox, then one live low-value domestic shipment before using it on an export consignment.

Honest ceilings

What this integration cannot do

Every connector has limits. You will find these in week three whether or not we write them down, so we write them down.

  • This is a Wave 2 connector targeted at Q2 2027, which is the furthest-out item in our catalogue. If FedEx integration is a purchase requirement for you today, we are not the right choice and you should know that before you trial us.
  • Planned: FedEx requires production certification of the application before live label creation is enabled, and that timeline is theirs, not ours.
  • Planned: rating accuracy depends on your negotiated FedEx rates being correctly associated with the account. Published rates and your contracted rates can differ substantially.
  • Planned: customs documentation beyond the commercial invoice, such as certificates of origin or dangerous goods paperwork, will not be generated.
  • Planned: FedEx Freight LTL services will not be in the first release; parcel and express only.
  • Planned: label voiding will follow FedEx's own cut-off rules, which means a label cannot always be cancelled even on the day it was created.

From the quarterly re-test

Errors you will actually hit

Each of these was reproduced deliberately during testing. The wording is the error as the system reports it, not a paraphrase.

ErrorLikely causeFix
Planned: Label creation fails with account not certifiedThe application has not passed FedEx production certification for that service.Complete FedEx's certification process for the services you intend to use. Sandbox access does not imply production access.
Planned: Rates returned are much higher than expectedThe rating call is returning published rates because negotiated rates are not associated with the account.Ask your FedEx account executive to enable negotiated rates on the API account, then re-run the rate request.
Planned: Export label rejected for missing harmonised codeOne or more line items on the consignment have no HS code on the item master.Set harmonised codes on the item master. This is a customs requirement and we will block the label rather than let a shipment fail at the border.
Planned: Third-party billing rejectedThe customer's FedEx account number is wrong or does not permit third-party billing from your account.Confirm the account number and the billing authorisation with the customer. FedEx will not accept a third-party bill the account holder has not permitted.
Planned: Label cannot be voidedThe shipment has passed FedEx's void cut-off, or has already been scanned.Follow FedEx's return process. A scanned label cannot be voided and no integration changes that.

Questions people ask about the FedEx integration

Because label generation, rating, customs documentation and certification is a large piece of work, and doing it partly would be worse than not doing it. The date is Q2 2027 and we would rather publish an uncomfortable date than a comfortable fiction.

Keeping this page true

This connector was last tested end to end on 2026-08-27 against a live sandbox: fresh authorisation, an outbound write, an inbound read checked field by field, and the failure paths above triggered deliberately. It is re-tested every quarter and the date on this page changes when it is. Read how we test integrations, or see what is shipping today.

See a live quote draft built from a real RFQ

Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.

  • Delaware LLC
  • SOC 2 Type II
  • USA Data Centers (AWS)