V1 pilot
Every unit. Every step. On the record.
Scale Axis routes, sequences and records everything that enters the depot. Request to shipment, and back again.
Clients
Petco
First client · V1 pilot
Anyone can demo a happy path.
This is what the system does on the other kind of day.
The scan is the truth.
The raw serial is stored exactly as it was read. Normalization happens server-side, so a scanner quirk never rewrites history.
Nothing happens without a record.
Every stage entry, clock start, pause and override writes an immutable audit event.
Blocked means blocked.
12 categories. A blocked unit cannot advance, and the screen names the exception holding it.
A connected system goes down. Work doesn't.
Writes queue with an idempotency key and retry on a 1, 5, 15, 60 minute ladder. A replay reuses the original key, so recovery never double-posts.
The clock is fair.
Turnaround runs from Ready for Processing, not from ticket creation. Waiting on someone else is not the depot's time.
No pause without a reason.
The API rejects one that has none, and reasons outside the depot leave the adjusted figure.
Asked twice, answered once.
A repeated webhook or an overlapping poll creates nothing twice. Every request is acknowledged exactly once.
Partial is normal.
A request can leave in several parcels. Each keeps its tracking number; a later one never replaces an earlier one.
Stock is what arrived.
Ten promised and nine delivered is nine on the shelf, and a discrepancy with an owner.
The flow
One path. No shortcuts.
9 stages. Four of them worked by hand.
- Intake
- Validation
- Routing
- Receiving
- Repair / Configure
- QA
- Fulfillment
- Shipped
- Closed
9
Stages
Intake to closed
12
Exception categories
Blocking or advisory
4
Integrations in V1
Added as clients need them
5
Routing dimensions
Down to a single store
Any number of systems. One record.
Every client’s depot runs differently, so Scale Axis is configured for each one, connected to their systems and the depot’s own.
Ready-made connectors
The goal is connectors for the well-known services in the industry, ready before a client needs them.
Custom where needed
If a system has no API, Broker Solutions builds a custom solution for it.
In V1, configured for the first client: 4 adapters, two of them pending.2
Jira Service Management
Read approved requests on an updated-since cursor. Write back a comment, the outgoing serial and the tracking reference. Never a status transition: the client resolves the ticket after the store confirms receipt.
Jira Assets
Read-only. Writes are built but disabled pending D3. The client reports Assets is a parts and categories reference layer today, not an asset repository.
Fishbowl
In scope for depot stock, bins and reservations. Interface pending D4: edition and access, part crosswalk, reservation and bin behaviour.
FedEx
No API call. The operator creates the label in the approved carrier tool and enters the tracking reference here. Tool pending D4.
Measurement
Three numbers. Raw and adjusted.
Both travel together, because an adjusted figure with no raw beside it is a figure nobody trusts.
Turnaround time
Configuration accuracy
Inventory accuracy
Roadmap
One platform. Six modules.
Planned, not built yet. In V1, Scale Axis is one application; the modules are what it grows into.3
Command
Orchestrate operations. Maintain control.
Pulse
Monitor health. Act in real time.
Signal
Surface insights. Drive decisions.
Flow
Automate workflows. Move work forward.
Relay
Connect systems. Transfer with trust.
Access
Central hub for access and orchestration.
What V1 is. And what it isn’t.
A short list that is true beats a long one that is aspirational.
In V1
- Client requests by signed webhook, reconciled by poll, acknowledged once
- Receiving with identity checks, repair, QA, allocate and ship
- Partial shipments, each parcel keeping its own tracking number
- Inventory by bin: deliveries, counts, adjustments with evidence
- One fulfilment owner per request, with override and rollback
- Writes to JSM limited to comments, outgoing serial and tracking
- Outbox with retry, dead letters, replay and restore
- Contract metric export, raw and adjusted
Not in V1
- The six platform modules: planned, not yet built
- Connections for other clients' systems: added per client, custom-built where a system has no API
- Okta and SSO: another provider behind the same session layer, not a rewrite
- Fishbowl: stock is held in Scale Axis until D4 confirms the interface
- Carrier label creation: the operator makes the label, and Scale Axis records the tracking number
- Jira Assets writes: read only until D3 names the authoritative register
- Closing JSM tickets: the client resolves the ticket after store receipt