ERP With Speedy Integration: How It Works and How to Start

TL;DR

• Speedy integration ends retyping. An ERP (the central system for your orders, stock and accounts) linked to Speedy handles 4 jobs: waybills, labels, tracking and cash-on-delivery payouts.
• Speedy's SOAP interface is retired. Speedy stopped supporting it on 30.09.2024 and fully decommissioned it in 2025, so connections now run on its REST API.
• There are 3 ways to connect. A native ERP connector, a middleware platform or a custom build, each with a different owner for upkeep.
• Fewer shoppers pick COD, but most still pay cash. Fewer than one in three Bulgarians choose cash on delivery, yet 78% of those who pay a courier directly still hand over cash.
• Match payouts every workday. Speedy pays COD money every workday, the day after delivery, so a daily match keeps any gap to one day of orders.
• Prim.io runs this at scale. Prim.io handles more than 3.1 million orders every month, and most brands go live in about 6 weeks.

If you ship with Speedy, you probably know the routine. Orders come in overnight, someone keys each one into the Speedy portal, prints the labels and then pastes the tracking numbers back into the webshop.

A day later, a Speedy bank transfer arrives with one total for dozens of parcels, and someone has to figure out which orders it covers.

An ERP with Speedy integration takes both jobs off your team's desk.

We build Prim.io, an ERP for brands and retailers with a native Speedy connector. This guide covers what the integration does, which setup fits you and how Speedy's COD money reaches you.

Table of Contents

• What Is ERP With Speedy Integration?
• What Speedy's API Lets Your ERP Do
• Three Ways to Connect Your ERP to Speedy
• The Order-to-Delivery Workflow, Step by Step
• Why Cash on Delivery Is the Hardest Part
• How to Set Up Your ERP With Speedy Integration
• When a Native Integration Pays Off as You Grow
• How Prim.io Handles Speedy
• Key Takeaways
• FAQ
• Conclusion

What Is ERP With Speedy Integration?

ERP integration with Speedy is a direct data link between your ERP and Speedy that automatically turns each order into a shipment. Your ERP sends the order details, and Speedy returns a waybill, label, and tracking number.

Later, Speedy's payout data flows back, so cash collected at the door lands on the right sale.

A few terms first. An ERP (enterprise resource planning) system is one platform that holds your orders, stock, purchasing and accounting, and our guide to what an ERP system does covers the full picture.

A waybill (товарителница) is the shipping document that travels with the parcel. It lists the sender, the recipient, the service and any cash the courier needs to collect.

Cash on delivery (COD, or наложен платеж) means the customer pays the courier when the parcel arrives, and Speedy passes that money on to you later.

Without an integration, every one of those details gets typed twice. Each copied address is a chance for a typo, and one typo can send a parcel to the wrong office.

According to Speedy company facts, Speedy holds "a market share of over 35%" of the Bulgarian courier market and runs more than 1,300 points, over 850 of them lockers.

What Speedy's API Lets Your ERP Do

An API (application programming interface) is a set of rules that lets two systems exchange data with no person in between.

Speedy uses a REST API, so your ERP sends simple web requests and gets answers back in JSON, a common text format for data.

According to the Speedy system integration page, the API covers address selection, office and locker selection, price calculation, shipment creation, label printing, courier pick-up requests and tracking.

That's nearly everything your team does in the Speedy portal today, so once the link is live, nobody needs to log in for routine shipments.

Before you trust an existing plug-in, though, check what it's built on. Older plug-ins used SOAP, an earlier messaging standard that Speedy ran under the name EPS.

Speedy's integration page is clear: "The development of new functionalities and technical support for this interface were discontinued on 30.09.2024, and it was fully decommissioned in 2025."

If your plug-in was set up before 2024 and nobody has touched it since, ask your vendor to confirm in writing that it calls the REST API.

The API serves your finance team too. The Speedy REST API documentation describes a payments service that can "Get shipment payout details for a period." Your ERP uses that data to match each COD payout to its order.

Three Ways to Connect Your ERP to Speedy

Every connection to Speedy follows one of three patterns: a connector built into your ERP, a middleware platform or a custom build. Middleware is a separate tool that sits between your ERP and Speedy and translates data from one to the other.

Read the table as a question of ownership. Each extra layer between your ERP and Speedy is one more place where a change on either side can stop your shipping.

For most brands, a native connector is the easiest to live with, because one vendor answers for the whole flow. That's the route we took with Prim.io.

Speedy is part of our catalogue of 50+ native integrations, and if you need something extra, the Prim.io API reference documents the endpoints for sales orders and delivery methods.

The Order-to-Delivery Workflow, Step by Step

Here's what happens to a single order once the link is live. Your team only steps in when something looks wrong.

• Order lands: A sale arrives from your webshop or marketplace, and the ERP records the street address or the chosen Speedy office or locker.
• Stock is reserved: The ERP holds the items so another sales channel can't sell them twice.
• Waybill is created: The ERP sends the shipment data to Speedy, which returns a waybill number that's saved on the order.
• Label prints: The warehouse prints the label as a PDF or in ZPL, the format thermal label printers use.
• Tracking syncs back: The tracking number attaches to the order and goes to the customer by email or SMS.
• Status updates: Delivery events update the order until the parcel reaches the customer.
• COD payout matches: When Speedy pays out, the ERP links the money to the sale and closes it.

Step 1 needs extra care in Bulgaria. According to the Bulgarian regulator's courier report published by BTA, "83% of consumers use courier services, while 70.1% prefer delivery to an office or locker."

Most of your customers, in other words, never give you a street address. Your ERP has to store the office or locker ID with the order, or Speedy can't create the waybill.

Step 7 is where many setups stop short. The Prim.io Speedy connector docs show the full loop, from waybill to completed sale.

Why Cash on Delivery Is the Hardest Part

Shipping is the visible half of the integration. The money is the half that keeps finance teams late at month-end.

The regulator's 2025 report, as relayed by BTA, found that fewer than one in three consumers choose cash on delivery. Those who do still lean on cash: a Payments Europe Bulgaria study reported by Economic.bg found that "When paying directly to a courier, 78% continue to choose cash over cards."

The two figures don't clash, since one counts who picks COD and the other how they pay. At a few hundred parcels a week, that's still dozens of payments to match.

How Speedy Pays You Out

Matching gets easier once you know how the money travels. According to Speedy's cash on delivery page, COD amounts are paid "every workday - Monday to Friday," by bank transfer or in cash at your address.

For domestic parcels, the money arrives on "the first workday after delivery of the shipment." Domestic COD paid out by bank costs 2.4% of the amount, with a €0.61 minimum.

Here's the catch. One transfer covers many parcels, and someone has to split it back into orders.

We call the failure mode COD drift. Small unmatched payouts pile up quietly each day, until month-end shows a gap nobody can explain.

The fix is to match on the same rhythm Speedy pays. Speedy pays every workday, so your ERP should match every workday too.

Payout details come per shipment, and your ERP already holds every order's waybill number, so it can match amounts without a spreadsheet. A daily match keeps any gap to one day of orders.

Two smaller COD settings are worth deciding early. Customers can pay the courier by card, which Speedy prices at 0.96%, and the API has a flag to switch card payment off if you'd rather not take it.

The second belongs with your accountant. The API can process COD as cash or as a postal money transfer, so agree which one fits your reporting under Ordinance N-18 before go-live.

When the Customer Opens the Parcel First

Many Bulgarian shoppers want to see the goods before paying. Speedy's API lets the customer open the parcel, or open and test it, before paying, and you choose who covers the return if they refuse.

A refusal hits two records at once: the COD won't arrive, and the goods are coming back. Your ERP should cancel the payment and expect the stock in one step.

For returns after delivery, Speedy's return voucher is a half-finished waybill the customer uses to send goods back within a period you set.

How to Set Up Your ERP With Speedy Integration

Setup starts with paperwork at Speedy and ends with a live COD test order. Settle each question below before moving to the next.

Most of the work is checking details, since a native connector already has the field mapping built in.

Do You Have a Speedy Contract and API Credentials?

• Sign a Speedy contract: You need an active business account before any API request works.
• Add a COD annex if you collect cash: Speedy's API documentation says sellers "could be required to have a valid contract and annex for COD for the destination."
• Request test credentials: Email api.registration@speedy.bg with your first and last name, company name, phone number and Teams name, if you have one.

Which Data Fields Need to Map?

Mapping means telling the ERP which of its fields fill each Speedy field. These five cause most of the errors.

• Sender and recipient address: The street and postcode must match Speedy's address format, or shipment creation fails. Speedy's API includes an address validation call, so use it before the waybill goes out.
• Office or locker ID: This field is required whenever the customer picks an office or locker over door delivery. Keep Speedy's office list synced so the IDs stay current.
• Parcel count and weight: These values drive Speedy's price calculation and appear on the label, so a wrong weight means a wrong shipping cost.
• COD amount: This is the exact sum the courier collects, in euros since Bulgaria adopted it on 1 January 2026. Speedy caps domestic COD at €5,112.41 per parcel, or €2,000 to or from a locker.
• Order reference (ref1/ref2): Put your order number here. It travels with the shipment and lets your team quickly trace any parcel back to its sale.

How Do You Test Before Going Live?

• Run test shipments: Create a few shipments for each delivery type you offer, such as door, office and locker.
• Check labels and tracking writeback: Print each label, then confirm the tracking number appears on the order. Speedy's tracking requests accept up to 10 parcels each, so batch status checks in groups of 10.
• Test one COD order end to end: Confirm the COD amount and reference reach Speedy, then check that the first live payout matches the sale.
• Test a refusal: If you offer open or test before payment, send one parcel that gets refused, and check that the expected COD is cancelled and the stock comes back.

Once you're live, match COD payouts every workday and review anything still unmatched once a week. The count of unmatched payouts is the one number to watch.

When a Native Integration Pays Off as You Grow

Each new sales channel or courier adds another connection to maintain. A brand that ships with Speedy often adds Econt, Sameday or BoxNow for coverage or price.

With middleware or custom code, each one becomes its own project. With a native connector, it's usually a setting.

The market still has room to grow. According to Eurostat, 78% of people in the EU bought something online in 2025, while Bulgaria's gap between internet use and online buying was 33 percentage points, one of the widest in the EU.

Our reading is that this gap leaves headroom, and every new online shopper means more waybills.

[QUOTE REQUEST: ERP courier integration]

Volume is where ERP integration software proves itself. Prim.io handles more than 3.1 million orders every month, and most brands go live in about 6 weeks.

If you're comparing systems, our list of the best ERPs for Bulgarian brands covers local VAT and courier needs. For warehouses and cross-border shipping, read our ecommerce fulfilment guide.

How Prim.io Handles Speedy

This section describes our own product.

Prim.io connects to Speedy natively, with no middleware. When an order is ready to ship, the connector creates the Speedy waybill and attaches it to the order.

It then tracks the shipment until delivery. For COD orders, it creates the payment at the cash desk you specify and completes the sale, so your order, stock and books close together.

Our setup documentation recommends running payment matching once a day rather than every hour. Speedy sits alongside Econt, DPD, BoxNow and Sameday in the same system, so adding a courier is a setting change.

Key Takeaways

• One link replaces the courier portal. An ERP connected to Speedy handles waybills, labels, tracking and COD payouts, 4 tasks teams often do by hand.
• REST is the only current option. Speedy ended support for its old SOAP (EPS) interface on 30.09.2024 and decommissioned it in 2025.
• Ownership decides the setup. Native connectors, middleware and custom builds differ mainly in who fixes the link when something changes.
• Office and locker IDs are essential. 70.1% of Bulgarian courier users prefer an office or locker, as reported by BTA.
• Match payouts on Speedy's rhythm. Speedy pays COD every workday, so a daily match keeps unmatched payouts to one day of orders.
• Prim.io is built for this volume. More than 3.1 million orders flow through Prim.io each month.

FAQ

Does Speedy offer a REST API for ERP and e-shop integration?

Yes. Speedy offers a REST API using JSON that covers address and office selection, price calculation, shipment creation, label printing, tracking and courier pick-ups.

Can you give me an example of ERP integration with a courier?

A webshop order flows into the ERP, which creates a Speedy waybill, prints the label and sends tracking to the customer. After a COD delivery, the ERP matches Speedy's payout to the sale.

Does Speedy's old SOAP integration still work?

No. Speedy ended support for its SOAP EPS interface on 30.09.2024 and fully decommissioned it in 2025, so integrations need the REST API.

How do I choose the right ERP integration approach?

Choose a native connector if your ERP offers one, and middleware if you must keep an ERP without one. Choose a custom build only if you have developers to maintain it.

What is an ERP integration platform?

An ERP integration platform, also called middleware or an enterprise integration platform, is a separate tool that moves data between your ERP and other systems such as couriers and webshops.

Conclusion

Connecting your ERP to Speedy automatically turns every order into a waybill, a label, and a tracked parcel. It also brings COD money back to the right sale, which is the part manual processes handle worst.

Our advice? Pick the option with the fewest layers you have to maintain, then match COD payouts every workday from week one. For most Bulgarian brands, that means a native connector inside the ERP.

To see the Speedy connector working on your own orders, create a free demo