Skip to content

Wholety operations guides

How to evaluate a wholesale ordering portal with one buyer order

A one-buyer trial separates what the portal shows from the sales draft, warehouse reservation and actual dispatch.

A wholesale ordering portal is useful only if the buyer's catalog, price and order reach the same stock workflow your team uses. Test that connection with one buyer, one SKU and one order before inviting every customer. A portal checkout and a warehouse reservation are different events; the trial should show both.

Set up a buyer order you can trace

Choose a representative merchant, an active product and one warehouse. Use a small test order with quantities you can verify. The example below starts with 100 cases physically in the warehouse, 35 already occupied by other orders and 5 locked. That leaves 60 available cases. The buyer requests 40.

Check Before checkout After the sales products save with selected stock
Physical stock 100 cases 100 cases until physical dispatch
Already occupied or reserved 35 cases 75 cases
Locked 5 cases 5 cases
Available for another buyer 60 cases 20 cases

Available = physical − occupied − locked. These example amounts assume the 40-case product save succeeds against the selected warehouse batches. If another order changes stock first, the save must be checked against the then-current records; a prior availability answer is not a promise.

Verify what the buyer sees

  1. Sign in as the buyer and confirm that only their permitted catalog and order history are visible. Staff and merchants use different menus and permissions.
  2. Check the price for this buyer and the unit in which it is quoted. Review any negotiated change using the required sales pricing permission; browsing access is not price-editing access.
  3. If the buyer calls the product by a different code, verify the merchant-to-internal-SKU mapping before adding it to the cart. Do not infer identity from a similar product name.
  4. Submit the cart once and find the resulting sales draft in the operations console. If checkout loses its response, inspect orders and the cart before retrying; the missing response does not prove that no order was created.

The partner SKU mapping guide covers versioned mappings. The B2B portal product page explains the supported buyer and staff workflows.

Verify when stock is reserved

Portal checkout creates a sales draft. Operations staff select warehouse batches and successfully save the sales products to validate and reserve stock. In this example, available stock would then fall from 60 to 20 cases. Dispatch is a later physical movement; it reduces physical and occupied quantities together. A cart, an empty draft or a read-only stock report does not reserve the 40 cases.

Open the saved order and stock records after each step. If the order products cannot save because stock changed, inspect the current availability and revise the proposed quantity instead of telling the buyer that the earlier 60-case figure is guaranteed. See how to prevent wholesale overselling for the two-salesperson case.

Ask your own AI Agent to check the same records

Connect an Agent with business read access and the appropriate merchant and stock visibility. Before checkout, ask:

For this buyer and item code, show the mapped internal SKU, the buyer's recorded price, and physical, occupied, locked and available stock in the intended warehouse. Name the source records and the time checked. Do not create an order or change stock.

After staff save the product plan, ask the Agent to read the resulting sales order and stock position again. Compare its answer with the portal order and warehouse screen. The Agent can explain the records it is permitted to read; it does not turn a read-only answer into a reservation. Connect your Agent before testing on your own records.

Decide whether this portal fits

This workflow fits when buyers need their own prices, catalog, cart and order history while your team controls warehouse allocation and fulfillment in the same system. If you must keep another ERP as the system of record, test that integration first. If buyers send purchase-order documents that must be parsed and automatically confirmed, verify that separate document workflow; a cart-to-draft portal does not establish it.

Start your free month with the clearly labeled example workspace, then close example mode before entering your own buyer and SKU. Use one test order to confirm the visible price, saved draft, batch selection and remaining available stock. The one-month trial includes the current features and one hour of consultation and assistance; no credit card is required.