Is this a manufacturing batch-record system?
The scope described here is commerce and operations: catalog, wholesale ordering, inventory, batch identifiers, COA documents and fulfillment. Linking an order or product to a batch document is not the same as recording or validating a manufacturing process. If manufacturing execution or electronic batch records are required, we scope those separately rather than treating a COA library as a substitute.
What should we ask to see in a peptide software demo?
Bring a sample catalog, a wholesale pricing rule and an order workflow. Ask to follow an approved buyer from account-specific pricing through the order and fulfillment record, then inspect how a batch document is matched and how a missing document is shown. Our Maddox Research case file illustrates wholesale and retail on one catalog; the 1776 RX case file shows commerce and fulfillment. Confirm which capabilities are part of your proposed implementation before committing.
What software do peptide and research-supply companies use?
Most start on a generic e-commerce platform with plugins bolted on for certificates, wholesale pricing and fulfillment. That works until you need a second brand, real batch provenance, or a payment method the plugin does not support. At that point operators either accept the limits or move to a custom platform. We build the second option — storefront, admin, certificate library and fulfillment as one system.
Can one backend run more than one brand?
Yes, and it is usually the right architecture. We resolve the brand from the request hostname, so each brand keeps its own domain, branding, catalog, certificate library and order numbering while sharing one codebase and one database. You pay for one platform instead of one per brand, and the brands stay genuinely separate where it matters — pricing and product composition can differ even when the product names match.
How do you handle certificates of analysis?
Certificates are scoped per brand and bound to batch identifiers rather than product display names. That prevents the most common failure in this category: two products sharing a compound name and surfacing the wrong supplier's document. Where a brand genuinely has no certificate for an item, the page states that instead of falling back to the closest match.
Do you build wholesale and broker pricing?
Yes. Wholesale tiers sit behind a login while public retail pricing stays open, both reading from one catalog. That removes the drift you get from maintaining a separate wholesale system, and it means a product only has to be created once.
What payment processors work for this industry?
Processor availability changes constantly and we will not promise you a permanent merchant account. What we do is put every payment method behind one interface with credentials in configuration rather than code, so card, Zelle, Cash App or crypto can be added or removed as a settings change. Losing a processor becomes an afternoon, not a rebuild.
How long does it take to replace an existing store?
It depends on catalog size and how much of the old system you can still reach. The compressed version is genuinely fast — in August 2026 we had two brands live and selling on a new platform before their outgoing developer took the original sites down, so there was no window where the business could not take an order. A planned migration with full access is more comfortable and produces a cleaner catalog.
Do you build the storefront, or just the back office?
Both, and they are the same system. The storefront customers see and the admin your team works in read from one database, so stock, pricing and order status cannot disagree between them. Splitting the two across separate tools is where most of the reconciliation work in this industry comes from.
Who owns the software when it is finished?
You do — the repository, the hosting account, the database and the domain, all under your own accounts. Given how many operators in this category call us precisely because someone else held those keys, we consider it the starting condition rather than a feature.