Use supported application boundaries.
Build authorized workflows against the platform interface while keeping private implementation details private.
Credentials and private endpoints never belong in public pages or client code.
Integrations
Connect inventory without creating a private back door.
Use imports, authorized exports, channel availability, API clients, and webhook endpoints against the same documented platform used by LTS Inventory itself.
Advanced integration operations begin with Control.
Connection workspaceLTS Inventory
01
Data movementMapped imports and authorized exports
Validated02
Application accessDocumented API clients and secure webhooks
Authorized03
Operational visibilityChannel state, reports, and delivery history
ObservableDocumented interfaces and visible delivery states keep every connection accountable.
Staged imports
Preview the shape of your data before it becomes inventory.
Match source columns to Inventory fields, validate rows, and review exceptions before an import changes operational records.
- Map familiar source headings to supported fields.
- Separate ready rows from records that need attention.
- Review validation results before committing the import.
A staged preview does not silently turn invalid rows into live stock.
Source fieldInventory fieldState
Item SKU→SKUMapped
Warehouse→Location codeMapped
Lot Code→Lot identifierMapped
Expires→Expiry dateValidate
Documented connections
Build on a visible platform contract.
Use documented interfaces and observable delivery states instead of hidden database access or one-off scripts no one can explain later.
Receive events with delivery visibility.
Understand what was sent, whether it arrived, and when a delivery needs attention.
Retries must not silently turn one event into duplicate inventory work.
Translate channel identifiers deliberately.
Keep external listings connected to the correct product and option inside Inventory.
Unresolved mappings and conflicts stay visible for review.
Webhooks and delivery
Know whether the message arrived.
Delivery history gives integrations an operational trail: event type, destination, attempt state, and recency without exposing secret values.
- Visible delivery and retry states.
- Event timing for troubleshooting.
- Clear separation between successful and pending work.
Delivery visibility is not permission to reveal payload secrets or customer data.
Illustrative event activity
inventory.updatedDelivered · just now
order.allocatedDelivered · 2 min ago
receipt.completedDelivered · 11 min ago
channel.syncReview mapping · 18 min ago
Freshness and conflict states
A sync should say how current it is.
Last-sync times, pending work, and conflicts help operators distinguish a fresh view from information that needs attention.
Fresh
The last completed sync is shown with a timestamp.
Pending
Queued work remains visible while processing continues.
Conflict
Competing mappings or changes are surfaced for resolution.
Disconnected
A failed or revoked connection is identified instead of appearing current.
Exports and reporting
Carry accountable records into the work that follows.
Use supported reports and authorized record retrieval to move information into review, reconciliation, or downstream processes.
Available formats and export scope follow the product’s current supported behavior; this page does not promise a private or undocumented export path.
Operational reporting
Review stock, movement, exceptions, and other supported operational views.
Authorized retrieval
Inactive subscriptions lock operations without removing the authorized record-retrieval path.
Choose the supported boundary
Put inventory at the center of the workflow.
Compare the current integration scope across Essentials, Operations, Control, and managed Enterprise before starting.