Skip to main content
GullySystem

API Integration for Online Stores

API integration connects the store to the systems behind it, and can expose an API for partners who need to read from you. The work covers field ownership, failure handling and who is alerted.

Share your requirements

Design before code

Two systems can be connected without any decision on which one is correct when they disagree. The design stage settles that first.

One owner per field

Price comes from the ERP, stock from the warehouse and customer from the store, for example. The choice is written down before work starts.

Matching keys

Item code, customer code and order number link both sides. Existing duplicates are cleaned up as part of the matching.

Frequency of sync

Orders can move at once, stock every few minutes and masters overnight. Real-time sync for every field costs more and is rarely needed.

Handling failures

The other system will be unavailable at times. The integration is built to expect that.

Queued, not lost

Messages are recorded before they are sent. After a restart they are replayed from that record, so an order is not dropped when a connection fails partway through.

Retries that back off

A few attempts are spaced out, then the item goes to a queue for a person. A struggling system is not hit repeatedly.

Reconciliation

Counts and totals on both sides are compared daily, so drift between systems is found while it is small.

Alerts to a named person

A failure goes to a specific person with the record identifier attached. It is not left in a log file.

An API for partners

A large customer or a marketplace may need to read your catalogue. The store can offer a controlled interface for that.

Keys per partner

Each partner receives a separate credential, which can be withdrawn at any time without affecting any other partner or your own systems. Access is easy to revoke.

Limits and versions

A rate limit stops one partner from flooding the system. Versioning means a change does not break their code.

Documentation

A page that the partner’s developer can read, so both sides avoid long email exchanges.

FAQ

Frequently asked questions

What if a system we use has no API?

There is often another route, such as a scheduled export, a database that can be read safely or a file drop. Where none exists, this is stated early and screen scraping is not used.

How do we know an integration is working?

Through a reconciliation report. Counts and totals are compared daily on both sides, and a message is raised when they differ.

Can you integrate with Tally?

Yes, through its import and export formats, usually on a schedule. Sales, credit notes, receipts and masters can move across using the ledger names your accountant already uses.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements