Helios One · buyer workflow
Plex automotive manufacturing supplier PO follow-up
The decision for this workflow
Start with a reviewed export and map release changes before discussing any tenant connector or portal access. The page uses sample/fictional data so a team can challenge the rule before sharing a real export. It is aimed at a buyer deciding what to ask, what to hold, and what to leave for a human.
Plex release export boundary map
This page’s working artifact is a Plex release export boundary map. It is intentionally narrower than a full ERP rollout: the buyer supplies a reviewed export or copies a supplier message, then checks the proposed state before anything is sent or written back.
Worked fictional example: Fictional Plex export row AU-PX-71
| Field | Fictional value |
|---|---|
| PO key | AU-PX-71 / line 20 |
| Supplier promise | 2026-12-12 / 900 units |
| Release revision | R5 changed to R6 after export |
| Decision | Flag stale export and request a fresh extract before follow-up |
The useful decision is start with a reviewed export and map release changes before discussing any tenant connector or portal access. In a real review, record the source file, message date, reviewer, and any redaction before treating a value as operational.
What Helios does directly
Helios can accept a reviewed CSV shape, map fields, and surface stale or missing values. P1 stores status records 0 live-tested integrations, so no Plex connection is claimed. Helios keeps the distinction between a draft, an extracted value, and a buyer-approved decision visible. A supplier reply is not sent automatically from this page, and no ERP record is changed by this artifact.
Evidence boundary
The Plex documents below describe vendor surfaces only. They do not prove a live Helios tenant, authentication, write-back, or portal bypass. The three sources below provide industry or vendor context; they do not establish a Helios customer result, certification, or live integration. The p1-stores status is the controlling integration boundary for this wave: 0 live-tested integrations.
Use the related workflow links to prepare the minimum export, draft an acknowledgment, or review a supplier reply. Keep real purchase orders and controlled documents in the approved environment.
Working artifact · fictional sample data
ERP route compatibility map
| Route | Evidence checked | Test status |
|---|---|---|
| CSV / Excel | Internal workflow brief | Working sample |
| Plex | Supplier manuals + official ecosystem | Tenant test needed |
| Epicor | Official docs link pending review | Unverified |
| Business Central | Official API docs | Unverified |
| NetSuite / SAP / Infor | Marketplace or product docs | Unverified |
Sources and verification
- Plex integration platform (primary; accessed 2026-10-23) — Plex documents integration surfaces; this is not proof of a live Helios connector.
- Plex partner ecosystem (primary; accessed 2026-10-23) — Plex describes its partner route; it does not list or validate Helios here.
- SourceDay PO collaboration datasheet (primary; accessed 2026-10-23) — SourceDay provides category context; its product is not attributed to Helios.
Frequently asked questions
Does this page mean Helios connects to Plex?
No. It shows an export-first mapping exercise and labels the live connector as unverified.