Operational Efficiency Through Shipping and E-Invoicing Integration

Turkeys e-invoicing threshold is 500k TL for e-commerce and e-arşiv now applies regardless of amount. The correct order of the order-invoice-shipping-return chain.

In e-commerce the post-order process is a single chain: the invoice is issued, the shipping label is printed, the tracking number reaches the customer, and the reverse flow runs when a return arrives. If any link in that chain is manual, the error rate climbs with order volume. This article covers Turkey's e-invoicing thresholds, integration methods, and how to build the flow.

Shipping and invoicing integration are usually treated as two separate projects. They are links in the same chain: order status triggers the invoice, the invoice triggers the shipping label, tracking triggers the customer notification. Built separately, manual transfers creep in between them — and that is where the real cost sits.

E-invoicing: who is in scope and when

On the regulatory side, 2026 is a decisive year for e-commerce sellers in Turkey:

Two rows matter most. First, the e-commerce threshold is a sixth of the general one: a seller reaching 500 thousand TL in revenue is in scope. Many stores that consider themselves small become obliged far earlier than they expect.

Second, the removal of the amount limit on e-arşiv: invoices below a certain value could previously be issued on paper, whereas now every invoice from a non-e-fatura taxpayer is issued as e-arşiv. Digital invoicing is no longer an exception even for stores with low basket values.

These thresholds and dates can change with regulation; confirm your own position with your accountant. The information here is a planning framework, not financial advice.

Integration method: the special integrator

In practice the most common route is a special integrator — a licensed technology firm authorised by the revenue administration, through which you issue and send invoices. The advantage is full integration with your accounting or e-commerce software: when an order completes, the invoice can be issued with a single click, or with none at all.

• API quality and documentation. This determines integration cost more than anything else.
• Return and cancellation flows. Issuing an invoice is easy; how return invoices, cancellations and corrections work in the API is where providers differ.
• Error reporting. How is a failed invoice attempt surfaced to you? Silent failure means a pile of unissued invoices at month end.
• Credit and limit structure. Cost should be predictable at your volume.

Shipping integration

Most setups implement the first two and skip the other two. Without status updates, customer service has to check the carrier's site for every query; without return matching, working out which order a package in the warehouse belongs to is manual. As volume grows, those two gaps take back the time the integration saved.

The correct order of the flow

1. Order is created — payment confirmation awaited.
2. Invoice is issued — with line items, VAT rates and customer details.
3. Shipment record is opened — label generated, tracking number written to the order.
4. Customer is notified — invoice and tracking number together.
5. Status updates are processed — the order closes on delivery.
6. Return flow — return request, return shipment, return invoice and stock intake.

The critical point is step two: the invoice must be issued before the shipment record. Built the other way round, you end up with orders that shipped but could not be invoiced, and correcting those retrospectively costs both time and compliance risk.

Error handling: where quality shows

• Invoice failed. Wrong tax number, missing address, or the service is unreachable. The order should move to an "unbilled" state and enter a queue — never be passed over silently.
• The same order invoiced twice. Retries need an idempotency key so the same request is not processed twice.
• Shipment created, order cancelled. The shipment record must be cancelled too, or paid-but-unsent shipping charges accumulate.
• Partial returns. When one of three line items is returned, the return invoice and stock intake must apply to that line only.

Every error scenario needs an alert and a manual intervention screen. The point of automation is not to eliminate errors but to isolate the failures and let everything else flow.

Compared with a manual process

In a store handling 50 orders a day, manual processing means entering invoice details into the accounting software, creating the shipment in the carrier panel, and passing the tracking number to the order and the customer — a few minutes per order, hours per day.

The real cost is not time but errors: a parcel sent to the wrong address, an invoice never issued, a tracking number that never reached the customer. Each comes back as customer service load and as lost seller score on marketplaces — as we cover in Trendyol store management, shipping performance is the fastest way to lose points.

Checklist

• Are you within the e-invoicing scope? (Confirm with your accountant.)
• Is the invoice issued before the shipment record?
• Is there an alert and intervention screen for failed invoices and shipments?
• Is there a control preventing the same order being invoiced twice?
• Are carrier status updates written back to the order?
• Is the return flow (return shipment, return invoice, stock intake) in place?
• Are partial returns supported?
• If you sell on several channels, are invoices consolidated in one place?

Common mistakes

1. Building only the happy path. Without error scenarios, automation makes problems invisible.
2. Opening the shipment before the invoice. You get shipments that cannot be invoiced.
3. Leaving the return flow for later. Returns are a normal part of e-commerce; retrofitted return flows are usually the most expensive development.
4. Skipping the threshold check. The e-commerce threshold is far below the general one; realising you are in scope late creates compliance risk.
5. Choosing an integrator on price alone. The real cost is in API quality and return scenario support.

Conclusion

Shipping and e-invoicing integration is the fastest-returning automation in e-commerce operations — because the work is repetitive, rule-based and expensive to get wrong. A properly built flow means doubling order volume without growing the team.

For the wider data flow, see ERP integration and ending manual data entry with API integrations.

At Commerslab we build shipping, e-invoicing and marketplace integrations including error scenarios and return flows. See our system integrations service or get in touch about your current flow.