The back-office stack for a research peptide company: spreadsheets, point tools or one system

The jobs behind the storefront

• Orders: every order, its status and what is on it.
• Payments: what was received, by which method, and which order it belongs to.
• Stock by batch: what is on the shelf, from which lot, and whether it can be sold.
• Lab reports: one per batch, current, and visible to buyers.
• Customers and wholesale buyers: who they are, what they bought, what they are verified for.
• Affiliates: attribution, commissions and payouts.
• Email and texts: consent, campaigns and order updates.
• Shipping: labels, tracking and packing slips.
• Suppliers: price sheets, purchase orders and landed cost.
• Wording: checking everything that goes out.

Option one: spreadsheets

Cheap, flexible and familiar. A sheet for orders, one for stock, one for payments and a folder of lab reports will run a small store.

• Works well: under roughly 50 orders a month, one person, one payment method.
• Breaks: when two people edit the same sheet, when payments arrive by several methods, when a buyer asks which batch they got, and when you need to know what is actually sellable right now.
• Hidden cost: the hours spent matching payments and answering "did my payment arrive?"

Option two: a separate tool for each job

A store platform, an inventory app, an email tool, an affiliate tool, a shipping tool, a spreadsheet for payments. Each is good at its job. Two problems appear in this category:

• Many general tools do not allow research-use-only sellers, or restrict them, so accounts can be closed without much notice.
• The tools do not share what matters most here. The affiliate tool cannot see a Zelle payment. The store cannot see that a batch is in quarantine. The email tool does not know which words to avoid.

Every gap between tools becomes a manual step, and manual steps are where orders go unpaid and batches get sold before they are cleared.

Option three: one system built for the category

One back office where the order, its payments, the batch that filled it, the lab report behind the batch, the affiliate who referred it and the emails about it all point at each other.

Signs it is time to move

• More than an hour a day spent matching payments or answering payment questions.
• You have sold, or nearly sold, stock from a batch without a current lab report.
• More than one person works in the back office.
• You are adding wholesale buyers or affiliates.
• A card processor or partner has asked for documents and it took days to assemble them.
• A tool account was paused or closed and you lost data or history.

How to move without breaking anything

1. Export customers, products and current batches to CSV.
2. Import into the new system and check the counts.
3. Run both side by side for two weeks: new orders in the new system, old orders finished in the old one.
4. Move payment instructions to include the new payment codes.
5. Switch the website connection last.

One more habit worth keeping

Finally, keep an export habit whatever you choose. Once a month, download your customers, orders, products and batches to a file you control, and store it somewhere separate from the system itself. It costs a few minutes, and it means no vendor decision, outage or account problem can ever take your records with it.

Who should own the back office

Whatever system you choose, name one person who owns it: who checks unmatched payments each morning, who releases batches, who reviews templates before they send. Software removes typing and remembering, but it does not remove decisions. Small teams that do well with any tool usually have one person who looks at the same few screens every day, at the same time, and a written list of what they check.

Write that list down before you move systems. It becomes the checklist for the migration and the training guide for the next hire.

A realistic migration timeline

• Day 1 to 2: import products, customers and current stock by batch; attach the lab reports you already have.
• Day 3: set up payment methods and payment codes, and connect your storefront or checkout.
• Days 4 to 14: run both systems side by side, entering new orders in the new one and checking totals against the old one each day.
• Day 15: stop entering orders in the old system and keep it read-only for reference.
• Month 2: close the old tools you no longer need.

The side-by-side period is the part people skip, and it is the part that catches the problems: a payment method that does not match, a product imported at the wrong strength, a customer who ordered under two emails. Two weeks is usually enough to see every common case at least once.

Questions to ask any vendor

• Will you serve a business selling research-use-only materials, in writing?
• Can I export all of my data, including customers and orders, at any time?
• How are payments that do not go through a card processor recorded and matched?
• Can inventory be tracked per batch, with lab reports attached?
• What happens to my data if I cancel?
• Who can see my customer list, and is it ever shared or sold?

The answers matter more than the feature list. A tool that works well but can shut you off without notice is a risk to the whole business.

What it costs to stay put

Moving systems has a cost, and so does staying. Add up the hours each week spent matching payments, answering where-is-my-order messages, updating stock counts and chasing lab reports. At a modest hourly rate, many small suppliers find the manual work costs more each month than software would.

Where Purity fits

Purity is one back office for research-use-only suppliers: payments on any method matched by code, batches released only with a passing lab report, wording checked before anything goes out, wholesale, affiliates, email and texts, shipping and suppliers. Plans are flat monthly prices and Purity never takes a cut of sales. Compare it with spreadsheets, WooCommerce plugins or general inventory tools, see pricing, or book a demo.