# Publish a supplier catalog on BuyingMesh

Merchant applications are open now at https://buyingmesh.com/merchant.html. The application is for real suppliers and authorized catalog owners. Historical internal test products are withdrawn and cannot be republished.

BuyingMesh accepts supplier-owned or explicitly authorized product data. Every submission stays private while the company profile, evidence, product facts, image rights, qualifications, price, inventory and lead time are checked. Only reviewed and supplier-confirmed merchant SKUs become public through REST and MCP.

## Data standard

Use one stable SKU per purchasable variant. The supplier profile must include a legal entity, contact, category, dispatch origin, authorization confirmation and image-rights confirmation. Each SKU should include its title, category, material, dimensions, MOQ (at least 100 units), unit price and currency, inventory state, lead time, HTTPS product images, source reference, qualifications and confirmation timestamp. MOQ is the minimum order constraint; inventory is a separate supplier-confirmed capacity field. Use `inventory_status=unknown` instead of guessing stock.

The complete field dictionary and jewelry-specific guidance are available at https://buyingmesh.com/merchant-data-standard.md. Download the UTF-8 CSV template at https://buyingmesh.com/merchant-template.csv.

The import form uses `sourcePlatform=merchant` and a 1× markup. The API accepts only merchant-owned or supplier-authorized sources. A batch over 5,000 rows is rejected instead of silently truncated. New rows enter `pending_review`; they are not public until the supplier and SKU are approved and current price, inventory and lead time are confirmed.

- Apply: https://buyingmesh.com/merchant.html#apply
- Data standard: https://buyingmesh.com/merchant-data-standard.md
- Field dictionary: https://buyingmesh.com/merchant-data-standard.csv
- CSV template: https://buyingmesh.com/merchant-template.csv
- Import contract: https://buyingmesh.com/openapi.yaml


