Operate your own B2B supplier or wholesale portal: catalogue, trade pricing, promotions, and customer-specific rules — without listing on someone else’s marketplace.
Operate your own B2B supplier or wholesale portal: catalogue, trade pricing, promotions, and customer-specific rules — without listing on someone else’s marketplace.
Buyers get self-serve price checks, order history, and messaging to your team. You keep margin, data, and relationships on your own domain.
Supplier catalog, orders, and book sales
For program owners/admins: Program owners/admins can enable customer payments with Stripe, PayPal, Square, GoCardless, Revolut, SumUp, Bank transfer, Cash from the shared Payment Settings screen on their own hosted copy.
Technical feature lists: full features · database package record
Choose how you want to start: use the free Starter on this site, upgrade to hosted cloud tiers, or compare against the self-hosted route below.
No program-subscription tiers are published for this product yet. Open the pricing page or start general registration.
Best if you want to register or log straight in and start using Supplier here without server setup.
Choose a hosted subscription if you want updates, backups, SSL, and support handled for you.
Ideal if you want your own infrastructure, branding control, or a package your team can deploy and manage.
License keys are issued uniquely per purchase. For typical self-host plans, one production hostname is registered on first successful validation/check-in and counts toward max_activations (usually 1). Moving to another domain normally requires a controlled deactivation of the old install or purchasing an additional seat — buyers should assume the binding is permanent for that URL unless your order terms say otherwise.
The installation phones home to your configured LICENSE_SERVER_URL (license_validate.php on use, license_check_in.php periodically). On the first production activation, the API may return license_binding_notice in JSON — installers should show that text once so operators understand the hostname pairing. Your administrator should schedule daily cron/license_enforcement.php on the license hub to reconcile dormant installs, payment status, and multi-domain breaches.
Payment standing: licenses store subscription status; validation rejects non‑trial/non‑active states (e.g. past_due, cancelled) so overdue accounts align with your payment defaults.
Commission-bearing features (where the platform owner earns on downstream sales) must be enabled per product and wired to your hub ledger — the nightly enforcement job can aggregate reseller commission where configured.
Payments & gateways: each self-hosted tenant must supply their own processor keys in admin payment settings. Do not ship or embed the vendor’s production gateway credentials in customer builds.
Owner/admin customer checkout options: all self-hosted program copies use the shared payment settings layer, so the program owner/admin can decide which providers their own customers see at checkout or on invoice links.
Cross-network listings & directory: optional federation (sharing listings across hub programs) and tiered directory placement are roadmap items — when enabled, tenants should keep sharing on unless they accept reduced discovery; eligibility is constrained by business type and subscription tier.
memory_limit — 512M or higher recommended for imports, image processing, and reportsmax_execution_time — 60+ for long-running admin tasks (some hosts cap lower)upload_max_filesize / post_max_size — Large enough for photography, documents, and CSV imports (e.g. 32M+ each)allow_url_fopen — Often required for webhooks and HTTP integrations (or use curl)Platform operators track activations, domains, and check-ins in the internal Licenses administration area; contact your vendor for domain transfers or resets.