POs, ASNs, delivery appointments, gate-in status and invoice status in one place for your vendors, and far fewer status calls for your team.
Five working areas that replace email threads and status calls.
Vendors see their own POs in open, work-in-progress, expired and closed views.
Vendors create and manage advance shipping notices against a PO.
Vendors view and book delivery appointments, with status views for each.
Vendors track whether their vehicle has arrived and been received.
Vendors see their invoices and the stage of each check, without calling AP.
Fields, plants and views are configured to your process, in several languages.
The Vendor Portal is where your vendors work with you. Instead of emailing a buyer for a PO copy, calling the warehouse for a delivery slot or asking AP whether an invoice arrived, a vendor signs in and sees the answer.
It connects to the rest of Cresolv One. The purchase order comes from your ERP, the appointment feeds the Gate-In Portal, and the invoice status comes from AP Automation. What the vendor sees is your live status, not a weekly summary someone compiled.
Most inbound vendor contact is a status question: do you have my PO, when can I deliver, did you receive my invoice, when will I be paid. Each one takes a few minutes from a buyer, a warehouse coordinator or an AP executive, and the answer is usually already sitting in a system.
Multiply that across hundreds of vendors and the cost is not the calls themselves. It is the interrupted work, the inconsistent answers and the vendors who stop trusting what they are told.
The PO area lists purchase orders in open, work-in-progress, expired and closed views. A vendor searches by their PAN, so they see only their own orders, and filters by ship-from city, GSTIN, plant and purchase document. Certain POs can be highlighted for attention, and lists export to Excel.
Buyers stop sending PO copies by email, and vendors stop working from outdated attachments.
An advance shipping notice tells the warehouse what is coming before it arrives. Vendors create ASNs against a PO and record supplier material code, EAN, HSN, quantity shipped, ship date and invoice number. The portal shows how much of the PO is still pending.
Field names and mandatory rules are configured to your process during scoping.
A warehouse that knows what to expect plans labour and dock time. The ASN also feeds the gate entry, so the delivery is matched at the door rather than argued about later.
Vendors book their own delivery appointments. Views separate appointments that are scheduled, not taken, missed and completed at gate-in, so the warehouse sees where slots are being wasted. Multiple appointments can be booked together, and exports are available in a standard form or as a detailed audit trail.
Fewer unannounced trucks means less yard congestion and fewer arguments about who was supposed to be where.
Two screens answer the questions vendors ask most.
A vendor can see that their invoice is waiting for a goods receipt, not lost, and your AP team does not have to explain it.
We would rather be plain about this. Purchase orders, ASNs, appointments, gate-in status and invoice status are live. Return-to-vendor management is on the roadmap and is not yet released.
Vendor access is by invitation. Each vendor sees only their own data.
The portal is the vendor-facing front of a connected flow. A vendor sends an ASN and books an appointment here. The vehicle is recorded in the Gate-In Portal against that appointment. The invoice that follows is matched in AP Automation against the PO and the goods receipt, and its status comes back to the vendor on this same screen.
You can begin with the portal alone, but the benefit grows as the three connect: fewer unannounced trucks, faster matching and almost no 'where is my invoice' calls.
The portal suits teams that deal with many vendors against purchase orders.
| Team | Typical pressure |
|---|---|
| Procurement | Constant status questions from vendors |
| Warehouse | Unannounced trucks and slot conflicts |
| Accounts payable | 'Did you receive my invoice' follow-ups |
| Manufacturers and distributors | Hundreds of active vendors across plants |
If you work with only a few vendors and deal with them directly, a portal may be more than you need today.
The portal is ERP-agnostic. Fields, plants, appointment rules and views are configured per client during scoping, and it can show several interface languages. Deployment and hosting are agreed per client need.
A pilot runs for about 45 days with a small group of vendors, often the highest-volume ones. We configure the portal, invite the vendors, and review how status queries, ASN quality and appointment adherence change.
Pilot results are indicative of what your own vendors will show, and we do not quote outcome figures before testing.
We do not ask you to rebuild anything. Pick a small group of vendors, configure the portal together, and see how status queries change.
Fields, plants, appointment rules and views set to your process.
A small group of high-volume vendors signs in by invitation.
Look at query volume, ASN quality and appointment adherence.
What procurement, warehouse and finance teams ask before opening a portal to their vendors. Read our full Buyer's Guide →
It is a self-service portal where your vendors see their purchase orders, create advance shipping notices, book delivery appointments, check the gate-in status of their deliveries and see which of their invoices are awaiting verification. It takes the status questions off your procurement, warehouse and AP teams.
By invitation. You invite each vendor, and they sign in to see their own data. Vendors cannot browse other vendors' purchase orders or invoices, because search is tied to the vendor's own registration.
They can view purchase orders in open, work-in-progress, expired and closed views, create and manage ASNs against a PO, view and book delivery appointments, track gate-in status for their vehicles and see invoices pending verification with the status of each check. Lists can be filtered by ship-from city, GSTIN, plant and purchase document, and exported to Excel.
A vendor creates an ASN for a shipment against a PO, recording quantities, ship date and invoice number. They then book a delivery appointment against it. When the vehicle arrives, the gate entry links back to the appointment, so your warehouse knows what to expect and your AP team can see the delivery arrive.
The invoice view shows each invoice with received date, invoice date, goods receipt posting date, delivered date and status, plus tick markers for the PO, GRN, vendor, business unit and booking checks. It answers 'was my invoice received and where is it stuck' without a phone call.
Yes. The portal is ERP-agnostic and configured to your process: the fields, plants, appointment rules and views are set up per client during scoping. Deployment and hosting are agreed per client need. Return-to-vendor management is on the roadmap and not yet released.
A pilot runs for about 45 days with a small group of vendors, often your highest-volume ones. We configure the portal, invite the vendors, and review the drop in status queries and the quality of ASN and appointment data together.
It is probably not yet the right fit if you work with only a few vendors and deal with them directly, or if you have no PO process for vendors to work against. We would rather say so on the first call.
Share a few details and we will set up a discovery call of about 45 minutes with a live demo.
Prefer chat? WhatsApp +91 7738829118 or sales@cresolv.com
Related reading
Fewer status calls, better delivery data and one view for vendors, with Cresolv One Vendor Portal.