Helios One · buyer workflow
Plex supplier updates without a supplier portal login
Design the smallest supplier touchpoint
Some suppliers answer an email faster than they create another portal account. This no-login route shows one purchase-order line, accepts a proposed date, and routes exceptions to a buyer while the ERP remains the system of record.
The practical sequence is: scope the supplier view to one line, accept a proposed date or plain reply, show the buyer what changed, and require approval before treating it as committed. The route is intentionally small.
Sample interface captures
These captures come from the v4 Helios Samples proof set and show the supplier portal interface with sample/fictional data. They are not screenshots of Caterpillar, Scania, Yield Engineering, or any other company’s private system, and they contain no private company data.
Caterpillar · sample/fictional data
Scania · sample/fictional data
Yield Engineering · sample/fictional data
Worked fictional example
The following is sample/fictional data for a Plex workflow. It is not a customer result or a live ERP record.
| Field | Example |
|---|---|
| Private view | PO PLX-9044, line 4 only |
| Supplier | Ridgeway Castings (fictional) |
| Requested | 24 cast housings by 2026-12-02 |
| Supplier input | Propose 12 on 2026-12-02 and 12 on 2026-12-09 |
| Buyer decision | Hold the second date for approval; do not close the line |
The browser artifact, Plex no-login supplier route map, gives this example a concrete review surface. It does not grant ERP access or silently change a promise date.
Evidence boundary
Public vendor and category documents describe procurement concepts and supplier-facing patterns. They do not prove that Helios has a live Plex connector. Any such connector is unverified. Keep the source export, review decision, and date change visible to the person who owns the PO.
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 Partner Ecosystem (primary; accessed 2026-10-23) — Plex's public partner route; it is not evidence of a tested Helios connector.
- Stant Plex Supplier Portal Work Instructions (primary; accessed 2026-10-23) — A public supplier workflow example for purchase-order and release details.
- NAL Supplier Purchasing Manual (primary; accessed 2026-10-23) — Public purchasing instructions that make acknowledgment and delivery details explicit.
Frequently asked questions
Is a no-login Plex portal live here?
No. This is a route map with fictional data. It does not expose Plex or send a token; any Helios connector or portal write-back is unverified.
What data should be real in a pilot?
Use an approved export and label every sample row. Agree on identifiers, date basis, partial-quantity rules, redaction, retention, and owner before sharing production data.