Wholety solutions

B2B ecommerce ordering portal and order management for wholesalers

Give wholesale buyers their own catalog, prices, cart and order history while your team manages stock and fulfillment in the same workspace. Start your free month with a complete example business, then connect your own AI Agent to inspect buyer item codes, available inventory and order records. No credit card or spreadsheet import is needed to explore the example.

Start free View plans and pricing

All features included, with no product or subaccount tiers. Connect your AI Agent or discuss your workflow.

Continue the Harbor Market story from the homepage

Your new workspace opens with the same oolong tea, ginger drink and sparkling water shown on our homepage. Check Harbor Market’s order history, compare the same stock and change the same question. The example is clearly labeled and read-only; close it in one click to enter your own data.

Review Harbor Market’s 90-day orders: 120 cases of HBT-24, 90 of GNG-12 and 60 of SPK-24.
Check the same available quantities: 60, 18 and 72 cases. An additional 48 of each leaves a 30-case ginger drink shortfall.
Open the source orders and warehouse records: the tea batch shown in the animation ends with 9 cases at A2 and 3 at B3.

Explore the example — start your free month

No credit card required. Understand available stock before promising the next order.

Ask your AI Agent what you can promise to the next buyer

Before your team confirms an order, ask your connected Agent to match the buyer's item code to your SKU and show physical, reserved, locked and available stock for the selected warehouse. Review the source records in Wholety. A portal cart or an empty sales draft is not a stock reservation: operations staff select warehouse batches and successfully save the order products to validate and reserve them.

Give merchants a focused ordering experience

Merchant accounts can browse products, open product details, add items to a cart and submit orders. The portal is the downstream customer's entry point into the trade system. Operations staff use the admin console for the broader purchasing, sales, warehouse and finance workflows, while the merchant role sees the merchant purchase menu.

Show prices for the relevant merchant

The default quote comes from eligible prices for the selected merchant. Staff with sales pricing permission can agree a different unit price, a whole-line discount or a free gift. The portal and API enforce the same permission, so browsing access alone does not let a customer change the price.

Move portal orders into the sales workflow

Checkout turns the saved cart into one sales draft, even when two submissions arrive together. New items added during checkout stay available for the next order. Operations staff then select warehouse batches and save the product plan to validate and reserve stock before approval and fulfillment. Merchants follow their own orders in the portal.

Confirm the quote before creating an order

The portal saves the confirmed quote and verifies the cart before submitting an order. A rejected price save or failed refresh stops checkout and keeps the form available for correction. Switching merchant or signed-in member stops the remaining work, so an earlier response cannot close the next merchant’s form or redirect their session.

Use roles to define the two entry points

The admin console and merchant portal share one account system. Their roles determine the available menus and operations. This setup suits B2B distributors serving downstream merchants who need product browsing and repeat ordering, while internal teams manage supplier purchases, warehouse stock and settlement. Review role and permission configuration before creating merchant accounts.

Match partner item numbers to your SKUs

Maintain a separate SKU correspondence table for each supplier or merchant. Review the complete table, stage additions and removals, then save with a version check. Existing internal SKU codes remain visible, and a colleague’s newer changes trigger a conflict so staff can reload and review before replacing the table. Read API Keys let agents inspect the same complete snapshots through HTTP or MCP.

Keep each delivery with the correct buyer

Plan multiple deliveries under one sales order, each with its own reference, contact and assigned whole order lines. Active addresses must belong to the order’s merchant. Reassigning a line moves it between deliveries in one transaction; a rejected save preserves the earlier assignments. Delivery planning stays separate from physical warehouse dispatch, delivered status and money collected. Read API Keys let agents inspect the same records through HTTP or MCP.

Try one buyer order before inviting your customers

Explore the labeled example first, then close example mode to start your own data. Add a representative product and merchant, and configure that merchant's price and role. Place one test order through the merchant portal, then open the resulting sales draft in operations. Select warehouse stock, save the product plan and compare the remaining available quantity. Ask your connected Agent for a read-only report of the same SKU and order, and compare it with the interface. Use the included hour of consultation and assistance to review your setup.

How the workflow fits together

Create product records and configure merchant pricing.
Assign the merchant role and review its permissions.
Let the merchant browse products and build a cart.
Submit the merchant order into the sales workflow.
Track fulfillment internally while the merchant views their own orders.

Common questions

Do merchants use the same back-office menus as staff?

The account system is shared, but access depends on the role. A merchant account sees the merchant purchase menu, while staff roles use the appropriate back-office operations.

Can a merchant track their own orders?

Yes. The portal includes a view of the merchant's own orders and their status, alongside product browsing, the cart and order submission.

What if the connection drops during checkout?

Check the sales orders and refresh the cart before submitting again. Wholety directs an uncertain checkout to order review; an agent should read the current order and cart records before deciding whether to try again.

Can I split one sales order into several delivery runs?

Yes. Add delivery records under the order and assign whole sales-plan or actual outbound lines to each run. A move updates the affected deliveries together. This assignment does not split a line’s quantity or perform physical stock-out; record partial dispatch through the warehouse workflow.

What happens if saving a quote fails before checkout?

No checkout request is sent. Some earlier line changes may already be saved, so refresh the cart, review prices and retry after correcting the problem. If the order submission itself loses its response, check sales orders first; a missing response does not prove that no order was created.

Does the ordering portal include AI access?

Wholety includes MCP access during the one-month free trial and subscription. Connect your own Agent to inspect the records permitted by its key, including partner SKU mappings and stock. Supported writes require business write access and review of the proposed operation. Your Agent's model-provider charges are separate.

Can it automatically turn a buyer purchase order into a confirmed sale?

This page describes catalog, cart and merchant order submission into a sales draft. Do not assume that an uploaded buyer PO will be parsed, matched and confirmed automatically. Test your item mappings and order workflow with your team; discuss document handling and integration requirements before relying on them.