Four weeks, included.
From your ERP to your first supplier signing in, with the person who built it on the calls. No implementation partner, no change order, no set-up fee.
Connect the ERP
Your IT team or ERP vendor produces three exports to our one-page spec: orders, deliveries and the supplier list. We connect them, agree the supplier account codes, and check the first schedule line by line against your order book.
Plants, users, costs
Your plants and currencies, your team with their plant permissions, standard costs for charges, your logo and name on the portal.
Pilot suppliers
Ten suppliers invited. Your team practises on the training supplier, a sandbox that behaves like a real one and never emails anybody.
Everyone in
The rest of the supply base invited in waves, reminder emails switched on, the first Order Status review on a Monday morning.
What go-live includes
- The export spec for your ERP, and every line of the first feed checked against your order book
- Plants, currencies, users and their plant permissions, standard costs, your logo and name
- Your existing concerns and 8D history imported from a spreadsheet
- Questionnaires, document requirements and 8D due days set up with you
- Pilot with ten suppliers, then the invitation waves, with the wording written for you
- Training for your team on the training supplier, and the help built into every page
What stays on your side
- Writing the three exports from your ERP: that is your IT team’s or your ERP vendor’s work, against our spec. They know your ERP and its database.
- The data in your ERP: supplier codes, part numbers and dates come across as they are. Cleaning them up is your ERP’s job, not the portal’s; the feed page shows you exactly what arrived, so nothing is hidden.
A word about the data in your ERP
The portal shows your suppliers what your ERP says. That is its strength, and it is also the thing to be ready for: a due date that was never maintained becomes a late order on a supplier’s screen, a supplier set up three times becomes three suppliers, and a delivery booked in without the delivery note number cannot be matched to the ASN. None of that is new; it was always in the ERP. What is new is that people outside the building can see it.
The first schedule is often the most useful data audit in years, because it is the first time anyone has looked at every open line at once. We check that first feed with you line by line, the feed page shows exactly what arrived each run, and duplicate supplier accounts can be merged in the portal without touching the ERP. Fixing the data itself, though, is done in the ERP by the people who own it. A portal that quietly corrected your order book would be a worse product, not a better one.
Your people see their plants.
A supplier sees only its own record.
Permissions by plant and role
Your people see the plants they are assigned. Suppliers see only their own record. Administrators assign both.
A record you can read
Every concern, 8D step, confirmation, verification and merge carries who did it and when.
A person at the door
Per-person accounts, a code from the phone at sign-in, and an account that opens pages faster than a person could is locked and reported.
See it with your own supply base.
A demo takes forty minutes. Bring a real supplier problem and we will walk it from the concern to the closed 8D, and show you the order book as your suppliers would see it.