Start with the procurement core, then expand into approvals, supplier collaboration, and sourcing visibility as the team grows.
For smaller teams moving off spreadsheets
For teams running approvals, follow-ups, and supplier collaboration at scale
For organizations that want shared commercial and execution visibility
| Capability | Core | Operations | Operations + Sourcing |
|---|---|---|---|
| Order book control | ✓ | ✓ | ✓ |
| PO PDF generation | ✓ | ✓ | ✓ |
| PO approval workflow | — | ✓ | ✓ |
| Email tracking and reminders | — | ✓ | ✓ |
| Supplier portal | ✓ | ✓ | ✓ |
| Supplier accounts and reset flows | — | ✓ | ✓ |
| Forecast sharing | — | ✓ | ✓ |
| Shortages and escalations | — | ✓ | ✓ |
| Sourcing dashboard | — | — | ✓ |
| Categories and managers | — | — | ✓ |
| Preferred and alternative sources | — | — | ✓ |
| Project material management | — | — | ✓ |
| Microsoft Graph support | — | ✓ | ✓ |
| Custom rollout support | — | ✓ | ✓ |
Yes. Onevyne is designed around import-driven operational workflows and supports mapped ERP exports, including SAP-style order data.
Suppliers can receive secure one-time links, create accounts, log in, confirm dates, upload attachments, and download documents from the supplier portal.
Yes. Supplier and material records are shared, with sourcing adding categories, preferred sources, alternative sources, quotes, and contracts on top.
Yes. Onevyne supports approval-driven PO workflows and feature flags so organizations can decide which users can see and use each PO step.
Yes. Onevyne supports Microsoft Graph as well as SMTP, depending on how your email environment is set up.
No. Teams can start with the procurement core and then roll out approvals, supplier collaboration, or sourcing capabilities in phases.