- Industry
- Retail
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- ENG-05
It connects the retailer's systems through their APIs and feeds: the e-commerce platform to the order management system, the order management system to the warehouse management system and carriers, the PIM to the marketplaces, and the tills to the loyalty platform. It maps the fields, handles errors and retries, and opens the integration change with its tests.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the order management system: the API contracts, sample payloads and current mappings for the systems named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request with the integration, its mappings and tests. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The integration catalogue: each system's API and file feeds, the field mappings (SKU, location, order and return ids), the error and retry patterns, the marketplace listing requirements and the credentials process.
Reads from
the order management system: the API contracts, sample payloads and current mappings for the systems named.
Acts in
the code repository: it opens a pull request with the integration, its mappings and tests.
Hands back
An object with mappings (a list of source_field, target_field and transform), error_handling (text), schedule, tests_added (a list) and pull_request_description.
Asks a person when
The integration sends shopper data to a new system or a marketplace, or changes how stock or prices reach a sales channel.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Retries before a message goes to the dead-letter queue | 5 | A failing message is retried this many times with backoff. |
| Most stock feed lag allowed (minutes) | 10 | Stock sent to the site and marketplaces may be no older than this, to avoid overselling. |
| Units held back from marketplaces | 2 | This many units per SKU are kept out of the stock sent to marketplaces. |
| Mask shopper data in integration logs | On | When on, names, emails, phones and addresses are masked in logs. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Map SKUs, locations and order ids through the master mappings; never match on product name.
- Retry failures up to 5 times with backoff, then send to the dead-letter queue with an alert.
- Keep stock feeds within 10 minutes and send marketplaces stock less 2 units per SKU.
- Every write is idempotent on the source id so a replayed message does no harm.
- When on is true, mask shopper data in logs; never send card data through an integration.
See the API Integration Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.