Item-level identity,wired into the stack you already run.
Twintag sits between the identifiers on your items and the systems that run your business. Every route reads and writes the same canonical item record, so nothing has to be rebuilt to get started.
Nine ways in,
one source of truth.
Pick the route that fits each system, from a developer API to a nightly file drop, and keep a single record behind all of them.
Connected to the systems
you already run.
The platforms our customers connect most, on protocols their teams already support.
Mapped, delivered
and scoped before anything goes live.
Integration work fails on field alignment, delivery guarantees and access control, so those three are settled first.
Mapped before anything is built.
We walk through your master data with your team and agree field by field how it lands on the item record, including units, formats and lookups. The mapping is signed off before the first call is made.
- Field level mapping per system, with transforms
- Units, date formats and code lists agreed up front
- Sandbox project to validate against real data
Events that arrive, or tell you they did not.
Scans, updates, publications and lifecycle changes are pushed as signed events with retries, replay and a delivery log, so your systems stay current and nothing goes missing quietly.
- Signed payloads with replay on demand
- Automatic retries with visible failure states
- Delivery log per destination and event type
Scoped access for machines, partners and agents.
Each integration gets its own token with the narrowest scope that does the job, a defined lifetime and a full audit trail, so opening up data to a partner never means opening up everything.
- Separate tokens per system, partner and agent
- Scopes down to read, write and issue per resource
- Rotation, expiry and revocation without downtime
- Every call logged with actor, scope and item