They said "we'll do an API integration" — how does the process work, and what's expected of us?

The single most critical issue is SKU mismatches. If the product SKUs on your e-commerce store don't match your accounting inventory codes character-for-character, the integration will blow up on day one. Before handing the work over to the devs, open a spreadsheet and manually verify that all your product codes align with the accounting system.

Get it in writing whether the integration is one-way or two-way. Are orders just flowing from the website into accounting, or will stock levels and price updates from the warehouse sync back to the website? Two-way sync involves API rate limits and conflict resolution logic, which adds substantial development time.

We did a similar integration last year. It took a full 9 days just to get the API license and sandbox credentials from our accounting vendor. The dev team finished coding in 12 days, but testing took an extra 8 days because shipping fees and line-item discounts kept posting to the wrong accounts. All in all, it took 29 days to go live.

Here should be your side's prep checklist: 1) Request the sandbox environment and docs from your accounting vendor. 2) Sit down with your accountant to define clear written rules for handling cancellations, returns, and split shipments. 3) Run at least 15 different test invoice scenarios before flipping the switch to production.

Is your accounting software cloud-based, or is it installed on a local server in your office? If it's running on an office computer you'll need a static IP and open ports to the server. That can create security vulnerabilities and also cause the integration to stop whenever the office internet drops; have you discussed this?

at first our accountant kept triggering errors on invoices for foreign customers without a tc kimlik numarası. if you take international orders or issue corporate invoices, figure out how those fields will be mapped right now, otherwise orders just end up hanging in the system.

edit: I wrote something wrong above, sorry about that.

Put your software dev team and the tech support from your accounting software into a shared email group or communication channel. You shouldn't have to understand the tech jargon or act as a middleman. Let the technical folks figure out the parameters and endpoints directly between themselves.

On our first integration we didn't want to pay 12.000 TL for a test environment so we tested directly on the live database. While the developer was issuing a test invoice, actual e-arşiv invoices and SMS notifications went out to real customers. That was the day we realized paying for a test environment is honestly the cheapest insurance you can buy.

Saved.

The answer above hits the nail on the head. The real issue isn't the number, but what it's based on.

Hasty decisions become decisions you have to fix six months later. I'm also curious if anyone does it differently.

There's a part I don't understand. If code ownership isn't in the contract, you have no bargaining power when leaving.

I'm also curious if anyone does it differently.

Let me share my experience. Access credentials should be opened in the company's name, not personal accounts.

Just leaving this note, it might be useful.

i agree.

Don't miss this: The cheapest quote is usually the least thought-out one.

If I were you I'd go this route.

The cheap-looking path usually ends up costing more later. Access credentials should be opened in the company's name, not personal accounts.

The biggest time-waster for us was not knowing who had the final say. If you have questions, write them; I'll answer as best I can.

Just a heads-up. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

If I were you, I'd go this route.

I went through the same thing. Weekly written progress reports are much more useful than asking for dates.

Start with a small trial; don't commit to everything at once. Good luck with that.

Thanks for writing this, that's the right way. Hasty decisions become decisions you have to fix six months later.

Don't hesitate to ask; those who don't ask always pay more. That's all, sorry if I went on too long.