Electrical / industrial distribution

Lumen

Public ERP page supports 850, 860, 855, 856, and 810, plus XML orders, web services, and real-time inventory/pricing integration.

Shared team packet

Jordan Hale owns this book · Harper Quinn covers

Roxanne confirmed punchout plus X12 still writes a second inventory file for regional DCs. They want one ERP truth before adding partners.

Next move
Bring a one-ERP-truth working session, not a new document-type pitch.

Returned coverage is now on this packet. The owner does not restart it.

Roxanne confirmed punchout plus X12 still writes a second inventory file for regional DCs. They want one ERP truth before adding partners.

Vendor, drop-ship, and special-order exceptions still sit with local autonomous branches. Lumen will hit the same coexistence if punchout partners expand.

So what do I do now?

PRIORITIZE · Instrumed Surgical

Lumen publicly supports the full 850→855→856→810 path—what still requires duplicate entry between your ERP, warehouse, and trading partners?

Who
Roxanne Plouffe · eCommerce Project Manager

Follow up
Approach integration or operations leadership with a document-flow and exception audit.

Prioritize
Do not start here. Open Instrumed Surgical first — the current book is waiting.

Who to call

First question

“Lumen publicly supports the full 850→855→856→810 path—what still requires duplicate entry between your ERP, warehouse, and trading partners?”

Why this conversation

Public ERP page supports 850, 860, 855, 856, and 810, plus XML orders, web services, and real-time inventory/pricing integration.

What the team can use

Approach integration or operations leadership with a document-flow and exception audit.

Public signal

Public ERP page supports 850, 860, 855, 856, and 810, plus XML orders, web services, and real-time inventory/pricing integration.