EDI for inventory updates

Concepts

What is EDI?

• EDI (Electronic Data Interchange) is how Themis-Trace automatically shares operational information with customers and partners.
• Instead of emailing spreadsheets or re-keying information into another system, EDI lets systems exchange the same facts reliably.
• For floor operations, EDI matters because it can:
  • Inform customers what inventory is available.
  • Keep customer systems aligned with the item details you maintain.
  • Reduce back-and-forth calls when information is already flowing automatically.

Think “message types” (not just “EDI”)

• EDI is not one thing — it is a set of message types.
• In inventory-focused workflows, you will most commonly hear about:
  • 846 (OUT) — inventory “snapshot” / advice (what is available)
  • 867 (IN/OUT) — item update (item details / attributes)
  • 870 (IN/OUT) — item status / condition updates
• You do not need to memorize technical fields. You do need to know which type is involved so you can describe issues clearly.

What actions trigger inventory-related EDI?

• Inventory EDI is typically triggered by one of two things:
  • A scheduled/system-driven send (for example, an inventory snapshot).
  • An approved change to inventory data that needs to be communicated externally.
• What this means for you:
  • If you correct an item’s attributes, it may flow out to the customer automatically.
  • If you change an item’s status/availability, it may flow out to the customer automatically.
  • If EDI is enabled for a customer, your changes can have external impact quickly.

The three inventory EDI types in daily work

EDI 846 (OUT): Inventory Advice (snapshot)

• What it is: a system-generated snapshot of inventory availability for a customer.
• When it matters to you: when customers say “your system says we have X, but we see Y” — the 846 is often the source of what they consumed.
• Typical operator impact: low day-to-day interaction, but it is a common troubleshooting reference when discrepancies appear.

EDI 867 (IN/OUT): Item Update (details)

• What it is: a message that communicates item details (for example, identifiers and attributes) between systems.
• When it matters to you: when you update item information (and especially when you correct identifiers used by customers).
• Typical operator impact: be deliberate with edits; mistakes can propagate externally.

EDI 870 (IN/OUT): Item Status (availability/condition)

• What it is: a message that communicates status changes (for example, whether an item is available, blocked, on hold, etc., depending on customer rules).
• When it matters to you: when placing items on hold, releasing holds, or changing statuses that affect whether an item can ship.
• Typical operator impact: status changes can affect what customers believe they can order, schedule, or pick up.

Use a “safe change” mindset when EDI is enabled

1. Before making a non-trivial change (identifier, status, Ship-To/Sold-To related metadata): confirm you are editing the correct item.
2. Prefer small, intentional corrections over broad edits.
3. If you are unsure whether a field is customer-facing, pause and escalate to a supervisor.
4. If a change needs to be reversed, treat it as a controlled correction (not an informal “flip it back”).

Where to verify transmissions for a specific item

• Navigate to the EDI Transmissions tab on the Edit Inventory Item form to confirm what the system has recorded for that item.
• Use this when:
  • A customer reports missing or incorrect EDI after an inventory edit.
  • You need evidence of what was sent/received and when.
• When escalating, capture:
  • Current customer
  • Item identifiers (Item ID and TTIN)
  • The time you made the change
  • The EDI type you expected (for example 846/867/870) and what you observe
  • Ensure that EDI transmissions have been enabled for the current customer context