Why does the back end of an order slow down?
In many companies, an order is created on the website in seconds, but the work behind it takes hours. Someone checks the bank panel to see whether the payment came in, enters the shipment on the carrier's website one by one, types the tracking number to the customer by hand, and issues the invoice separately in the accounting software. Every step is a wait, and every copy is a chance for an error.
Payment integration
With virtual POS (payment gateway) or payment provider integration, the payment is automatically linked to the order. A successful payment moves the order to "confirmed," and a failed payment is reported to the customer. Installment options, 3D Secure verification and refunds all run through the same integration. Card details are never stored on your system; the payment page runs on the payment provider's secure infrastructure.
In B2B sales, payment by bank transfer or against a current account is also common. In that case, we set up the matching of each collection with the corresponding transaction on the customer's account in the ERP.
Shipping integration
With shipping (carrier) integration, a shipment record is created automatically with the carrier as soon as the order is confirmed, the barcode label is printed in the warehouse, the tracking number is added to the order and sent to the customer by email or SMS. The delivery status is read back as well, so the order moves to "delivered" on its own. If you work with more than one carrier, choosing the carrier can also follow rules based on region or volumetric weight.
E-invoice and e-archive integration
If you are registered for e-invoicing, your invoices go out through an accredited e-invoice provider. With integration, the invoice is generated automatically from the order data: if the buyer is registered for e-invoicing, it is issued as an e-invoice (e-Fatura); if not, as an e-archive invoice (e-Arşiv), and then delivered to the customer. The invoice number is written back to the order and the ERP. That way, the accounting team only checks invoices instead of recreating them.
End-to-end example flow
| Step | What happens | Who does it |
|---|---|---|
| 1 | Customer pays by card | Payment integration |
| 2 | Order is confirmed and drops into the ERP | ERP integration |
| 3 | E-archive invoice is issued and sent to the customer | E-invoice integration |
| 4 | Shipment is created, label is printed | Shipping integration |
| 5 | Tracking number is sent to the customer | Automatic notification |
| 6 | Delivery status is recorded on the order | Shipping integration |
In this flow, the only physical work left for your team is packing the product.
Checklist
- The bank or payment provider you work with and your virtual POS details
- Contracted shipping carriers and your customer numbers with them
- The name of your e-invoice provider
- Invoice series and numbering scheme
- At which stages the customer should be notified
These flows carry customers' names, addresses and contact details; we build KVKK (Türkiye's Personal Data Protection Law) requirements into the design and don't charge extra for it.
Frequently asked questions
Do we have to switch e-invoice providers?
Usually not. We can work with the connection services of the widely used e-invoice providers, so your current agreement stays in place.
Can we use more than one shipping carrier at the same time?
Yes. The carrier can be chosen per order, either by hand or automatically based on rules.
These integrations are a natural part of our e-commerce projects. For our overall approach, go back to the integration services page, or get in touch.