ERP With Econt Integration: How It Works and What to Automate

Every morning, someone on your team copies addresses from last night's orders into Econt, one at a time. They print the waybills and hope nobody typed "ул. Шипка 14" as "ул. Шипка 41."

Then month-end arrives. The same people sit with a bank statement, trying to match each COD transfer to the right order.

An ERP with Econt integration takes most of that work off their desks. In this guide, we cover what it automates, how to set it up and which connection path suits your shop.

We'll also get into the parts most guides skip, like partial refusals and how COD money actually reaches you.

And the volume is only growing. According to the Bulgarian E-commerce Association's BEA PASSPORT 2025 summary, online sales in Bulgaria in 2025 are "estimated at over 2.69 billion euros," which is "an approximate growth of 15% compared to 2024." Every extra order needs a waybill, and somebody has to make it.

What Is an ERP With Econt Integration?

An ERP with Econt integration is a business system connected directly to Econt's API. Orders automatically turn into waybills, while tracking statuses and cash-on-delivery payments flow back into your orders and accounts.

A few terms help here. An ERP (enterprise resource planning) system runs sales, stock, purchasing and accounting in one place, and here's what an ERP system does in more detail.

An API (application programming interface) is the set of rules that lets two systems exchange data automatically.

A waybill (товарителница in Bulgarian) is the document Econt needs for every parcel. It carries the sender, recipient, weight, service and any cash to collect, so one typo can cost you a delivery.

Most shops start with Econt's free webshop plugin, which handles checkout prices, office selection and labels. For a small store, it does the job.

Trouble starts as orders grow. The plugin lives inside the webshop, while your stock, invoices, and COD money live elsewhere.

An ERP connection closes that gap. Once an order ships, the warehouse knows what to pick, and finance knows what cash is on its way.

Running a global ERP such as SAP or NetSuite? Check early whether it has an Econt connector or needs an add-on or custom code. We built Prim.io in Sofia, and Econt is one of our native integrations.

What the Integration Automates, From Order to Payment

Every Econt order moves through five stages: order, waybill, pickup, delivery and payment. A good integration handles all five in one system.

Weaker ones tend to stumble at the last stage, where the money is. For the warehouse side, including picking and packing, see our ecommerce fulfilment guide.

Waybills and Courier Pickups

Once an order is confirmed, the ERP fills in the Econt waybill from data it already holds, including the customer's name, address, phone, parcel weight and COD amount.

The label PDF lands on the order, and your packer prints it with one click.

Before that label prints, though, it pays to check the address. Econt's API documentation includes address validation alongside label creation, courier requests, tracking and office data.

The check takes a second. A parcel that bounces back can cost you shipping both ways.

From there, the ERP requests a courier pickup from your warehouse, or you drop the parcels at an Econt office. Our Econt integration generates waybills and schedules pickups natively, with COD amounts and statuses tied to each order.

Shipping Costs and Office Delivery at Checkout

Before a parcel leaves, the ERP shows its shipping cost, so you see each margin while you can still act on it.

The same price can appear at checkout, where the customer chooses an address or an Econt office.

In Bulgaria, the office usually wins. The Communications Regulation Commission's 2025 courier report, as reported by BTA, found that 70.1% of consumers prefer delivery to an office or locker, and 83% use courier services.

Lockers are spreading fast, too. The same report counts 3,725 across the country, 18% more than a year earlier.

Your ERP therefore needs a current list of Econt offices that refreshes on its own. When a customer picks one at checkout, its details go straight onto the waybill.

Tracking and Status Updates

The ERP pulls each shipment's Econt status into the order record. Support sees exactly what the customer sees, next to the stock movement and invoice.

Those statuses should also trigger the next step. A delivered parcel moves the order to payment, and a refused one tells the warehouse to expect goods back.

Cash on Delivery and Reconciliation

Cash on delivery (COD, or наложен платеж) means the courier collects payment at delivery and transfers it to you later.

The habit is fading. The regulator's report found that fewer than one in three consumers now choose COD.

Even so, a shop shipping a few hundred parcels a week still handles dozens of cash payments. Each one needs matching to an order.

Matching gets easier once you know how the money travels. According to Econt's developer documentation, COD can be paid out to a bank account, in cash at an office or at your address.

Adding your COD agreement number to the waybill lets Econt automatically credit the collected amount to that agreement.

The route you pick also changes what you pay. BizzUpp's September 2026 breakdown of Econt's tariffs puts bank payouts at 1.62% with next-day transfer, against 3.24% for cash.

For most shops, the bank route is the obvious choice.

It does bring one puzzle. The money arrives as one transfer covering many parcels, minus fees, and someone has to split it back into orders.

Done by hand, that job eats up month-end afternoons.

In Prim.io, the system creates the COD payment at your chosen cash desk as soon as the parcel is delivered, then completes the sale. Our Econt setup documentation also recommends syncing payments once a day instead of every hour.

One last COD decision belongs with your accountant. Econt can process COD as a postal money transfer, which affects your fiscal receipt obligations under Ordinance N-18.

Either way, make sure your ERP sends the same COD setting on every waybill.

Refusals, Returns and Inspect-Before-Paying

Bulgarian shoppers often want to open the parcel before paying, and Econt turns that into a waybill setting. Its developer documentation describes three levels.

Review gives the customer 15 minutes to inspect the parcel and pay only if they accept it. Review and test adds the right to try the product in that window.

Review, test and select goes furthest. The customer keeps some items from a multi-item parcel and returns the rest.

Offering these builds trust at checkout, but it complicates your records.

Under the select option, Econt requires an itemised list that totals the COD amount, plus return instructions. Rejected items return as a separate shipment, and you decide who pays.

Without an integration, each partial refusal becomes three manual jobs: restocking the items, lowering the expected COD amount and correcting the invoice.

An ERP should handle all three from the status update. If a vendor can't show you one working in a demo, assume your team will do it by hand.

How to Set Up Econt in Your ERP

With a native integration, setup is mostly gathering details and testing, with no code to write. Start with the checklist, then follow the steps in order.

What You Need Before You Start

Have these ready before you open a single settings screen:

• An e-Econt user account, either your existing one or a new registration with Econt.
• The API username and password for that account.
• The address of every warehouse you ship from.
• Your webshop payment methods, each mapped to COD or prepaid.
• Your COD payout details, including your COD agreement number if you have one.
• Your return rules, including who pays when a parcel comes back.

Setup Steps in Order

Follow these steps in order, and resist the urge to skip the tests.

• Add Econt as a delivery method in your ERP.
• Enter your Econt API credentials.
• Test in the demo environment first. Econt's API documentation notes that the demo and production endpoints (web addresses) are different, so test shipments stay separate from real ones.
• Set a default package type for most of your orders, and check Econt's weight limits for each service.
• Set payment defaults, including who pays for shipping, how COD is collected and where payouts go.
• Turn on any inspect-before-paying options you offer, with matching return instructions.
• Sync the list of Econt offices into your ERP.
• Choose whether couriers collect from your warehouse or you drop parcels at an office.
• Run one test order through checkout, waybill, delivery and payment, then a second that ends in a refusal.
• Switch to the production environment and ship your first real order.

Econt and the Euro: What Changed in 2026

According to the ECB Bulgaria euro changeover page, Bulgaria adopted the euro on 1 January 2026 at a fixed rate of 1.95583 lev per euro.

For shipping, the switch touched every waybill and every COD amount.

Econt handled the awkward part itself. Its API documentation states that, from 01.01.2026, waybills created in advance in Bulgarian lev "will be automatically converted to euros," with no changes needed.

One rule stays with you, though. The same documentation says "a currency must be provided for COD/declared-value services." Declared value is the parcel value you state for insurance.

In practice, check two things. Your ERP should send a currency on every COD waybill.

It should also keep older lev orders and new euro orders in the same records, so a return on a December 2025 order still adds up. Prim.io has multi-currency built in.

Native Module, Middleware or Custom Build: Which Path Fits?

You can connect Econt in four realistic ways. Each one changes who does the work, and who fixes things when Econt updates its API.

Econt's plugin sits inside your webshop, while a native integration is built into the ERP itself.

Middleware, often a TMS (transport management system), is a separate shipping tool between your ERP and your couriers. A custom build is code your developers write against Econt's API.

For most growing brands, we'd pick native. You get one set of order records and one vendor to call when something breaks.

In Prim.io, the Speedy courier connection runs in the same system as Econt, alongside Sameday and BOX NOW lockers. A second carrier doesn't mean a second tool.

Prim.io has 50+ native integrations across webshops, marketplaces, payments and couriers. A custom build only makes sense for unusual flows, such as a special returns process.

Even then, the Prim.io API lets your developers add those pieces on top of the native Econt connection.

Before you sign with any vendor, put these questions to them:

• Does it create the waybill and request the pickup without leaving the order screen?
• Does it send a currency on every COD waybill?
• Does a delivered COD parcel create the payment and close the sale automatically?
• Can it handle a partial refusal, restocking the items and adjusting the COD amount?
• Can you test everything in Econt's demo environment before going live?
• Who updates the connection when Econt changes its API?

Vague answers usually mean manual work creeping back a few months after launch.

Whichever path you choose, size it for growth. According to Eurostat e-commerce statistics 2025, 27% of internet users in Bulgaria "did not buy or order goods or services online in 2025," against 15% across the EU.

As that gap narrows, your order volume grows.

Frequently Asked Questions

What does an ERP with Econt integration do?

It turns orders into Econt waybills, pulls tracking back into each order and connects COD payments to your accounts.

Do I need a developer to connect Econt?

With a native integration, usually not, because setup means entering credentials and choosing defaults. You only need one for a custom build.

Can I test the integration without real shipments?

Yes. Econt runs separate demo and production endpoints, so you can create test waybills before going live.

How does cash on delivery work with an ERP?

The courier collects the money, Econt pays it out, and the ERP records the payment against the right order. In Prim.io, delivery creates the COD payment and completes the sale.

Can I use other couriers alongside Econt?

Yes, if your ERP connects more than one courier. In Prim.io, Speedy, Sameday and BOX NOW run in the same system as Econt.

What happens when a parcel is refused or only partly accepted?

The refusal shows up on the order, and the goods come back as a return shipment. A good ERP restocks them, adjusts the expected COD amount and corrects the invoice.

Conclusion

An ERP with Econt integration takes the copy-paste out of shipping. Waybills, pickups, tracking, refusals and COD all run from the same order.

If you only run one test while comparing vendors, make it this one. Ask to see a delivered COD parcel and a partly refused one go from order to books, live.

The system that handles both without a spreadsheet is the one worth paying for.

Comparing options? Start with our list of the best ERPs for Bulgarian brands.

Prim.io handles more than 3.1 million orders every month, and our customers go live in about six weeks on average. See the Econt flow with your own orders.

Create a demo account

Prefer a walkthrough? Book a session. No sales scripts