How to connect FanCourier with easySales: a complete setup guide
Connect FanCourier to easySales: every field on the connection form, why the service type decides whether your AWBs go out, how to run several accounts, and what each FanCourier refusal means.
What connecting FanCourier gives you
With FanCourier connected, easySales creates the AWB for an order, prints the label, tracks the parcel, cancels the shipment and can call the courier for a return — without you opening FanCourier at all.
This guide covers the whole connection, and it starts with the field the old documentation never mentioned — Service type — because that single choice decides whether your AWBs go out at all.
Before you start
A FanCourier account with API access
FanCourier issues an Account ID, a username and a password for it. The Register entry in the card's ⋮ menu tells you how to ask for them if you do not have them yet.
Your Account ID to hand
It is the numeric client code, not your username. It is sent with every request and a wrong one stops everything with The client id do not exists...
The service your contract uses
Know whether the orders on this connection are cash-on-delivery or prepaid, and which FanCourier service covers them. It is the field that decides whether AWBs go out.
One connection per set of options
One service, one set of credentials, one set of options per connection. Two warehouses, or both payment types, means two connections — running more than one is the normal shape here.
Step 1 — Open the Couriers page
Go to Integrations → Couriers and search for fancourier. In the newer navigation the same page sits under Integrations → Delivery → Couriers.
Press Connect on the FanCourier card. If you have no FanCourier contract yet, the ⋮ menu on the card has a Register entry that tells you how to ask for one.
Step 2 — Enter your credentials and press Get Details
Fill in Connection Name, Account ID, Username and Password, then press Get Details.
Connection Name is yours alone — it never reaches FanCourier. It is the name you will pick from when you create an AWB, so name it after the warehouse or the service it ships with.
Step 3 — Choose the service type
This is the most important field on the form, and the one that causes most avoidable failures.
The Drop-off point field below it is easy to misread:
Step 4 — The rest of the connection
| Field | What it is for |
|---|---|
| Connection Name | Required. Your own name for this account. It is what you pick from when creating an AWB, and it never reaches FanCourier. |
| Account ID |
Required. The numeric client code of your FanCourier account. It is sent with every request; a wrong one comes back as The client id do not exists...
|
| Username and Password | Required. The credentials FanCourier issued for API access. easySales signs in with them by itself and refreshes the session as needed, so there is nothing to reconnect later. |
| Service type | The FanCourier service every AWB from this connection uses. See the step above — this is the field that decides whether an AWB can be created. |
| Drop-off point | The FANbox you hand parcels in at. Only used when the service is FANbox. |
| AWB Format | A4 or A6 — the size FanCourier renders the label at. A6 is the thermal-label size. This is sent to FanCourier; it is not a printer setting. |
| Saturday delivery | Adds FanCourier's Saturday delivery option to every AWB from this connection. |
| Open package | Adds FanCourier's open-on-delivery option, which lets the recipient check the contents before paying. |
| Shipping payer | Who FanCourier bills: Sender or Receiver. Return connections also offer Recipient and Third party. |
| Send order ID as internal reference | Sends your easySales order number to FanCourier as the shipment content reference, so it appears on their side and on your invoice. |
| Notes template | What is printed in the observations line on the label. Cut at 97 characters. |
The Notes template box sets what is printed in the observations line on every label from this connection. The buttons above it insert values from the order and from its products — order ID, invoice series, quantity and SKU, warehouse location.
Step 5 — Printing settings and advanced options
Both sections are collapsed and neither is required.
| Setting | What it does |
|---|---|
| Paper size / Scale type | Only used when you print through the easySales Printer connection, and only for this courier. They override the printer's own defaults. This is not the same as AWB Format: FanCourier decides what the label looks like, these decide how it lands on paper. |
| Cost center | Up to 40 characters, sent on every AWB from this connection. FanCourier shows it on the invoice, so it is the simplest way to split courier costs between shops, warehouses or sales channels. |
| Generate packages based on the number of packages of the product | Counts the parcels on the AWB from the package count on each product in the order, instead of always sending one. |
| Auto call courier | Return connections only. Asks FanCourier to collect the parcel as soon as the return AWB is created. |
Several FanCourier accounts
A connection carries one set of credentials, one service and one set of options. Ship from two warehouses, or ship both cash-on-delivery and prepaid orders, and you need two connections — that is the normal shape here, not an exception.
To add one, open the ⋮ menu on the FanCourier card and choose Connect another courier account. To copy an existing one, open it and press Clone: everything is duplicated and " (cloned)" is added to the name, which you should then change.
Each connection keeps its own credentials, service, options and notes template, and appears by its Connection Name when you create an AWB.
Return AWBs
On the FanCourier card the form has two tabs, Delivery account and Return account. A return connection is a connection like any other, plus the address the parcel comes back to.
Two fields behave differently on the return tab:
- Shipping payer also offers Recipient and Third party. Choosing Third party adds a Third-party payer name box, and that name is what FanCourier bills.
- Auto call courier appears under Show advanced options. With it on, easySales asks FanCourier to send a courier to collect the parcel as soon as the return AWB is created.
Creating AWBs
| From | What you get |
|---|---|
| Quick Create on the orders list | Choose FanCourier, then the connection by its name. One AWB, straight away, using everything set on that connection. |
| Create AWB on the order page | The same, plus what a connection cannot hold: envelopes, parcels, total weight, dimensions and the cash-on-delivery value. |
| The orders list, several orders selected | One AWB per order, all on the same connection. |
When FanCourier refuses an AWB
The message comes back from FanCourier unchanged and is shown on the order. Almost every refusal is one of the reasons below.
| What FanCourier says | What to do |
|---|---|
COD (cash on delivery) is required for this service type
|
The order has nothing to collect and the service on the connection is a cash-on-delivery one. Use a connection whose service accepts prepaid shipments — for most contracts that is Standard. |
COD (cash on delivery) is forbidden for this service type
|
The reverse: the order has money to collect on a service that does not take it. |
The cash on delivery field can only be filled if the client accepts card payment
|
Your FanCourier contract does not allow collecting the amount the way this order is set up. It is settled on the FanCourier side, not in easySales. |
Not allowed to create awb
|
FanCourier is refusing the account itself — usually a contract that is suspended or has no AWBs left on it. |
The client id do not exists...
|
The Account ID on the connection is not a client code FanCourier recognises. |
Locality is invalid
|
FanCourier does not recognise the town on the order. Correct the address on the order — bear in mind that a Bucharest sector is sent as Bucuresti automatically, so sectors are not the cause.
|
The recipient.address.zip code must not be greater than 6 characters.
|
The postal code on the order is too long. Romanian codes are six digits. |
awbGeneration.info.options.fanBoxDropOffOrPickupOptionRequired
|
A FANbox service with nowhere to hand the parcel in. Set a Drop-off point on the connection, or send the order to a locker. |
The selected info.service is invalid.
|
The service saved on the connection is not on your FanCourier account any more. Press Get Details and choose one from the refreshed list. |
The info.observation must not be greater than 255 characters.
|
The notes template produced too much text. Shorten it. |
An error occurred
|
FanCourier's own catch-all, and it says nothing more. It is worth retrying once; if it repeats on every order, the account needs FanCourier's attention. |
These credentials have expired
|
Nothing to do. easySales signs in again by itself and repeats the request. |
Cancelling an AWB
easySales can delete a FanCourier AWB, and it passes FanCourier's answer back unchanged.