Skip to main content

Get Ready for Wholesale

Use this checklist to prepare one sound wholesale relationship before expanding the range or extending more credit.

Step 1: Prepare the business

  1. Complete registration, email confirmation, business verification, and multi-factor authentication.
  2. Confirm Wholesale is selected in Settings.
  3. Review the current supplier terms in Supplier Portal. This handbook is not the acceptance record.

Step 2: Prepare the first range

  1. Create the initial wholesale products in Catalog, or use a bulk file for a load.
  2. Give every sellable item a unique, stable stock-keeping unit (SKU).
  3. Set a wholesale list price and any minimum order quantity. Your private cost is not offered to sellers and does not replace a missing wholesale price.
  4. Make sure sellable products are active and supported by accurate product information.

Step 3: Set honest stock

  1. Set starting stock in Inventory, or use an inventory file.
  2. Set reorder points for every item you replenish.
  3. Validate low-stock and incoming views.

Step 4: Agree the seller relationship

Review pending requests and set commercial terms:

  • Discount percentage
  • Credit limit
  • Payment terms days
  • Dropship as an additional supply model, if relevant

After approval, you can update the wholesale credit limit and record the reason. Other commercial terms require a fresh agreement or marketplace coordination.

Step 5: Prove one purchase order

Validate the full wholesale path before scaling volume:

  1. Confirm the purchase order in Orders.
  2. Ship it with tracking.
  3. Ask the connected seller to record goods receipt in Partner Portal, then verify the resulting delivered and invoice records.

Do not mark the purchase order delivered from Supplier Portal. Seller receipt is authoritative for received quantities and marketplace invoice issue.

Step 6: Set the operating controls

  1. Decide who reviews purchase orders, credit exposure, shipment exceptions, and overdue remittance.
  2. Keep Supplier Portal as the fallback for fulfilment work.
  3. Send technical teams to Developers only when an approved business-system connection is needed.