ATPL

Services · Engineering

Make the systems you already own work together.

Stop retyping the same order into three tools. We wire payments, order feeds, Tally, SMS and your own software — and publish APIs partners can trust.

2016
Third-party order intake since
2014
Centralised cloud reporting since
16
Years building technology
List the handoffsHow Ethos takes outside orders

Connectors

Connectors that fail in the open

Payments, Tally, messaging and your own API — with logs you can read when the other side blinks.

  • Tally without the month-end dump

    Invoices and ledgers pushed on a schedule, with a reconciliation when totals disagree.

  • Messages from events, not from memory

    SMS, WhatsApp Business and email fired when an order is placed, a bill is due or a delivery leaves.

  • An API you can show a partner

    Versioned, keyed, rate-limited and documented so apps and dashboards read and write safely.

  • Sync that survives a bad afternoon

    Scheduled and live jobs between databases — the outlet-to-cloud pattern Ethos has run since 2014.

Primary deliverable

Ships with the engagement

Live brief

01 · Lead outcome

Orders and money in one place

Gateways, UPI, aggregators and marketplace feeds into one system — Ethos has taken third-party and mobile orders since 2016.

  • 01Tally without the month-end dump
  • 02Messages from events, not from memory
  • 03An API you can show a partner
  • 04Sync that survives a bad afternoon

How it ships

Handoffs, then switches

List every retype. Pick the system of record. Ship each link behind a feature switch.

  1. link/01

    List the handoffs

    Every system, who owns it, what it exposes, what is still typed by hand — ranked by hours saved.

  2. link/02

    Pick the system of record

    Direction, frequency and what happens when the other side is down, written down before code.

  3. link/03

    Live behind a switch

    Each link ships with logs you can read. A failed sync is visible before missing data is.

  4. link/04

    Vendors will change the goalposts

    Under support we watch error rates and update connectors when the other side ships a breaking change.

Still typing

The human is the integration

If someone is still keying orders between three apps, the link is missing — not the diligence.

List the handoffs

  • Orders

    Orders land from three apps and a website. Someone keys each one into billing by hand.

  • Ledger

    The accountant gets a monthly export and finds the mistakes a quarter later.

  • Partner

    A partner asks for an API. There is nothing safe to hand them.

In production

Work we can put a name to — or the method we will use until we can.

Chosen for the job

Node.js · Laravel · Python · PHP

Decide the shape

Tally, downtime and cost

Plain answers on accounting pushes, vendor breakages and how long a connector takes.

Two systems exchange data on their own instead of a person copying it. We connect payments, order apps, accounting and messaging — and build APIs so partners can connect to you.

Yes. Invoices and ledger entries go on a schedule with reconciliation, so accounts work from live data. The same pattern covers other common Indian packages.

The link should fail in the open and retry: queues, readable logs, an alert to a person. Ethos has taken outside orders since 2016 through several vendor changes.

A payment gateway or SMS provider is often one to three weeks. Several systems with sync and error handling are quoted after a short discovery; support covers later vendor changes.

Continue to