What counts as a regulated or documentation-heavy product?
Anything where selling it carries obligations beyond the transaction — required labelling, test or compliance documentation, restrictions on who may purchase, or destination rules. Supplements, cosmetics, food, chemicals and licensed health products all land here.
Can you work with our existing compliance requirements?
Yes. We map the obligations first — what has to be recorded, shown, restricted and retained — and build them as structured data rather than as plugins bolted onto a general platform. We build to the requirements you give us; we are not your compliance advisor.
How do you handle required labelling?
Generated from structured fields rather than retyped per product. Retyping is how labelling drifts, and drift is invisible until somebody audits it.
Can you restrict who is able to buy certain products?
Yes, and enforced server-side on the request that creates the order — not merely hidden in the interface. Hiding is presentation; enforcement is what makes a restriction real.
What happens if we lose our payment processor?
Payment methods sit behind one interface with credentials in configuration rather than code, so adding or removing one is a settings change. We will not promise you a permanent merchant account — nobody honestly can — but we can make switching cheap.
Do you provide an audit trail?
Yes, from day one. Who changed what and when, recorded as it happens — because history cannot be retrofitted once the question has already been asked.
