Your assortment. One place to work from.

Give buyers a maintained catalog to find articles and prepare requests. Give your team the products, quantities and contacts together, ready for review.

Keep the assortment. Structure the conversation.

  1. Maintain your assortment

    Import a supported CSV or XLSX file with reviewed article, product-name, unit and number mappings. Check the preview and import results before publishing your company catalog.

  2. Receive a clear request

    Authorized buyers search articles or product names; published guest catalogs provide exact article lookup. Buyers review selected products, permitted quantities and contact details before submitting a stored purchase request.

  3. Review it together

    Your authorized manager opens contacts and product lines together and updates the local processing status. A Simple request starts a review; it does not confirm payment, stock reservation or fulfillment.

A workspace that follows the customer.

Enable the native capabilities your company needs. Current customer permissions control what each buyer can see and do.

Managed buyer access

Grant and revoke access to a customer account. Share a one-time invitation link with an expiry; automatic invitation email remains unavailable. Buyers see their own permitted company resources.

Customer-specific prices

Assign explicit customer price lists with currencies and units. Buyers see current permitted prices; missing, stale or unsupported pricing requires clarification rather than an invented price.

Observed availability

Show warehouse observations with their timestamps and current, stale or unknown state. An observation helps review a request; it is not a stock reservation or availability guarantee.

Local orders and history

Permitted buyers review and submit a local order, then see their own history and local status. Repeat builds a new editable list for review against current products, quantities and prices.

Connect deliberately. Verify the source.

Supported ERP read connectors and protected company configuration are implemented. Each deployment needs its own authorized access, explicit product/customer/price/warehouse mappings and verified reads.

Native catalog and buyer capabilities can work with managed or imported data. Genuine external provider acceptance is deferred; installed connector code does not mean a connected ERP.

ERP order creation, external status updates and payments require separate authorization and actual readiness. Local order statuses describe the application’s own records.

Company setup and access are managed by an authorized owner or manager. Existing account holders can sign in.