An employee needs a replacement headset. The company has a supplier agreement, but the employee cannot find the right catalog or tell which cost center to use. Buying the headset personally and filing an expense seems faster. The amount is small. Repeat the choice across departments and the business loses visibility into commitments, contract usage, and the reasons employees bypass the preferred process.
An eProcurement platform brings routine purchasing online, typically through guided buying, requisitions, approvals, and purchase orders. It can connect with sourcing, suppliers, receiving, or accounts payable. Evaluate the employee journey from intent to receipt. Strategic procurement can negotiate a good agreement, but eProcurement determines how easily someone can use it when a purchase needs to happen.
Start with the words employees use to search
Employees often search for what they need rather than a supplier’s exact description. Use real search terms and confirm that the right items appear. A headset could be listed as a communication accessory, a meeting device, or a specific model. Category trees, synonyms, and curated recommendations can reduce the gap, provided someone maintains them as catalogs change.
Guidance should depend on the requester’s organization and location where relevant. Different legal entities may use different suppliers or prices. Two departments can have different ordering restrictions. Test a user whose home location differs from the delivery site, and another person who requests items for someone else. The interface should make the applicable catalog and accounting context clear before checkout.
A good guided buying experience also helps when no item fits. Offer a clear route for a non-catalog request with an explanation of what happens next. Ask for details that help a buyer act, such as the service location, specification, or requested date. Measure how long the employee spends searching before reaching this path and how often procurement has to ask for the same information again.
Choose how each supplier catalog is maintained
A hosted catalog is maintained or imported into the buying platform, giving the buyer control over searchable items and fields. A PunchOut workflow sends the employee from procurement into a supplier’s catalog, where they build a cart and return the selected lines to a requisition. Coupa documents this supplier catalog pattern, and SAP documents catalogs in its guided buying workflow. Coupa PunchOut catalogs · SAP guided buying catalogs
A hosted catalog can be appropriate for a stable set of commonly purchased items. PunchOut can make sense for suppliers with a large range, configurable items, or prices maintained on their own site. Evaluate both from the employee’s perspective. Returning from a supplier’s site with a cart should retain item identifiers, agreed prices, currency, and units of measure. Confirm how restricted items are screened and what happens when a price changes before the purchase order is issued.
Take one supplier through onboarding in the trial. Ask who loads and tests the catalog, who checks negotiated prices, and who monitors rejected orders. Simulate a supplier site outage and a cart with a discontinued item. Check whether the requester can preserve their work and whether procurement can offer an alternative. Supplier maintenance is an ongoing commitment, especially when several business units share catalogs.
Put approval where a decision still matters
A requisition requests permission to buy. A purchase order communicates the approved commitment to the supplier. The platform should make the distinction clear to requesters and buyers. Test whether a buyer can consolidate requisitions, split one requisition across suppliers, or return a request for changes while keeping the original history.
Approval may depend on cost center, amount, commodity, or the nature of the request. A routine contracted item may need a budget approval. A non-catalog software subscription may require several types of review. Use the shortest route consistent with your policy. An approval chain designed for every possible edge case can make ordinary purchases slow enough that employees look for other ways to buy.
Send a requisition to a manager who is away, then change the quantity after approval. Ask what the employee sees, who can act as a delegate, and whether the changed amount triggers a new approval. Confirm that delegation respects scope and duration. The interface should also show the difference between a rejected request, a request awaiting more information, and one waiting on a budget decision.
Keep purchase orders and receipts connected
A purchase order can be sent through a network, supplier portal, electronic integration, or email. Test how delivery and supplier acknowledgment are represented. An order may have been transmitted successfully while the supplier has yet to accept the price or delivery date. If a supplier accepts only part, the buyer needs to see which lines can proceed and which need follow-up.
Receiving is where the business confirms goods or services arrived. A warehouse receiver may record quantities against a line. For services, a department may approve a milestone. Ask how the system treats partial receipts, returns, and services that are accepted over time. Finance should receive the references it needs to reconcile the supplier invoice against the purchase order and receipt where that policy applies.
Integration design matters even when buying feels simple. Specify which system owns suppliers, accounting codes, budgets, and purchase order numbers. When an ERP rejects an order because a cost center closed, the requester and buyer need different levels of detail. Give the support team enough context to fix the mapping while the employee sees a clear explanation and next step.
Evaluate adoption by looking for workarounds
A deployment can show many active users and still leave meaningful purchasing outside the approved process. Compare eligible spending with actual requisitions or orders, and inspect the reasons for exceptions. Some categories may intentionally use other channels. In other cases, slow catalog search, missing suppliers, or repeated approval delays explain why employees choose a different path.
Pilot with regular buyers and occasional users. Include one hosted catalog order, one PunchOut purchase, a non-catalog service, an absent approver, and a partial receipt. Track time to submit, approval delays, support requests, and the quality of the transaction reaching finance. Ask whether the catalog and approval owners can fix the most common issues without a lengthy release cycle.
A useful eProcurement platform gives the employee a short path to the right item or request. It also gives procurement and finance a dependable record of the commitment. If staff can find the approved option, understand the status, and complete receiving without switching to email for ordinary exceptions, the pilot has tested the reason to buy the system.