Erli + Apaczka
Send parcels with Apaczka straight from your Erli orders. The address on the order turns into a label, and the tracking number comes back to the order card.
What you get
Sending and tracking parcels for the Erli + Apaczka pairing
Erli with no extra setup
Erli orders drop into the shared despatch queue on a single API key, with no OAuth and no separate panel.
Several carriers on one account
Through one connection to Apaczka you send with different carriers and pick the service separately for each order.
A label without retyping the address
The address, the phone number and the chosen delivery method come off the order onto the label automatically, so you never copy them into the carrier's panel.
Single and batch printing
Pull a label for one parcel or for a whole batch of orders at once, and with a configured printer the print starts without downloading a file.
Tracking comes back to the order
We save the parcel number and the delivery status on the order, so you check them without opening the carrier's site.
Carrier selection rules
You decide which order goes with which service, by weight, by amount, by country or by the delivery method the buyer picked.
How do I connect Erli to Apaczka?
Connect your Apaczka account
Generate an application identifier and secret in the Apaczka panel and paste them into NavyFlame.
Connect your Erli account
Generate an API key in the Erli seller panel and paste it into NavyFlame. No OAuth, one key is enough.
Set your shipping rules
Decide which orders from Erli go with Apaczka and with which service, by weight, by amount or by the delivery method the buyer picked.
Send and print
From now on you prepare a parcel with one click from the order list, and the tracking number comes back to the order card in Erli.
Why this integration?
Erli hands over the delivery address in an order pulled with a single API key, so the road from order to label is short and needs no OAuth. Apaczka is a broker that gives you several carriers through a single connection, so you can compare services without signing a separate contract with each of them. NavyFlame joins the two sides: it pulls orders from Erli, prepares the parcel with Apaczka and sends the tracking number back to the sales channel. This integration does not issue invoices and does not sync warehouse levels, that is what the separate integrations with an accounting system and with an ERP system are for.
Frequently asked questions
In NavyFlame you connect your Apaczka account and your Erli account, set the shipping rules and send from the order list. The address and the chosen delivery method come off the order onto the label, and the tracking number comes back to the order card.
Apaczka sits in the middle: one account gives you several carriers, but the terms come from the broker. Connecting a carrier directly uses your own contract and your own rates.
Yes. The connectors run side by side, and your shipping rules decide which order takes which route.
No. The Erli + Apaczka pairing handles shipping: the label, the despatch and the tracking. Invoices are issued by a separate integration with an accounting system, which you connect alongside this one.
No, that is what a separate integration with an ERP system does. Shipping uses the orders that are already in NavyFlame and does not change what the warehouse shows.