Test payments.
Cards are not being charged. Orders will still settle, dispatch and pay out as if they had been.
This page is out of date.
A newer version of SourceRX has been deployed.
Viewing - as a SourceRX administrator. Actions here change this partner's real data.
Partner Home
Everything for your product business.
New products available
Recent activity
Live orders
Watching for new orders…My store
Overview
Setup
My store
Shelf
On your shelf
Changes save as you make them, and a live shop stays live.
Available to add
Approved for your account and not on your shelf yet.
My store
Look
Name and address
Your approved DBA. It sets your shop's link.
-Available
Your pages
Design your front page and add pages of your own, like About or FAQ: drag in sections, text, images, products and your own code. Nothing changes for customers until you publish.
Shown on your storefront and on your terms and privacy pages, so your customers write to you. Leave it empty and SourceRX support is used instead.
Your logo
PNG, JPEG or WebP, up to 256KB. Shown in place of your store name at the top of every page.
or drag one here
Your colour
Used for buttons and highlights. Text on top is set automatically to whatever stays readable.
#1557d5
Your headline
How the headline at the top of your front page is set. The compliance notice above it always stays.
My store
Delivery
Who pays for delivery
Shipping is $16.00 flat per order, once, however many vials. Pass it on to your customer, or cover it yourself. Covering it does not change any of your prices; it comes off your margin.
Leave Free over empty for no threshold. Setting it to 0 makes every order ship free.
Free delivery codes
A customer types one of these at checkout and pays nothing for delivery. You still cover the $16.00.
My store
Domain
Connect your domain.
Your store answers at your own web address. Your customers never see ours.
Use a subdomain such as shop.yourbrand.com or store.yourbrand.com. You keep your main website exactly where it is.
Add this record at your domain provider
One record, once. Sign in wherever you bought your domain, open its DNS settings, and add:
TypeCNAME
Name / Host
-
Value / Points to
-
If your provider offers a proxy or CDN toggle on the record, leave it off, a proxied record hides where it points, and the check that brings your store up cannot see through it. Some providers call the Name field a Host, and some want just the first part rather than the whole address, both are shown above.
My store
Announcements and wording
Announcements.
A short line that runs across the top of your shop. Up to eight, up to 120 characters each. Switch one off to keep the wording without showing it. Saving these never takes your store offline.
Write about your own shop, hours, dispatch days, how to reach you. Nothing here may name another business, and none of it may describe what a product does or is for.
Words on your shop.
Buttons, headings, labels and messages. Anything you leave alone keeps our wording, and changing your mind later is one press of Reset.
The research-use notice, the age question and the payment line are not here and cannot be changed. They say what this system actually checks, so a shop cannot word them into saying something else.
My store
Ad tracking
Your ad accounts
Add your Meta Pixel, Google tag or Hyros script and your shop reports page views, add-to-carts, checkouts and purchases to them. Paste the whole snippet or just the ID; we keep the ID.
Ad tracking is not available on a
prescription (503A) shop. A pixel there would tell Meta or Google which patient is buying
which preparation.
Events Manager → Data sources → your pixel. Sends PageView, ViewContent, AddToCart, InitiateCheckout and Purchase.
G-… for Google Analytics 4, AW-… for Google Ads, up to three separated by spaces. Tag Manager containers (GTM-…) are not accepted.
Goals → Conversions → your purchase action → Tag setup, the send_to value. Needs the AW-… ID above.
Hyros → Settings → Tracking script. This tracks visits and ad clicks.
Hyros → Settings → API. With a key saved, every paid order is sent to Hyros with the buyer's email, phone and IP so it can match the sale to the ad.
Your shop's privacy notice names whichever of these you turn on, and says what each one is sent.
Orders
Orders from your storefront.
Buy stock
Buy in bulk, at the tier your order earns.
Shipping to your customer
Optional. Cover it yourself, or let your customer pay it at checkout.
Add quantities to price your order.
Your requests
My inventory
Stock you own.
Payouts
What you have earned.
Card fees are taken by the payment processor before the money reaches SourceRX. They are shown here so your figures reconcile, SourceRX does not receive them.
What you made, order by order
On stock you had already bought, the whole sale is paid to you, your profit is that sale less what those units cost you.
Activity
Stock requests
Partners asking to buy in bulk.
Already decided
Refunds partners have asked for
On a Kashu Pay payment, approving sends the refund through Kashu and books it. If Kashu refuses, the request stays here with Retry refund. On any other processor, approving only decides it: you issue the refund in that processor, and the books update when it confirms.
Payouts
The book.
Processor fees appear as deductions. They are kept by the payment provider out of each charge and never reach this business.
Where each order's money went
Four separate cuts. The processor's is kept by the card company and reaches none of the other three.
Activity
Affiliates
People who send you customers.
Commission is a share of the goods on an order, after any discount the customer got, and it comes out of your margin, not off what you pay us. A code that would take an order below what it costs you is refused at checkout rather than quietly reduced. It is deducted when the order settles and shows on your payouts as a line of its own, and an affiliate cannot be paid until the order is past the window a customer could ask for their money back in. A refunded order returns its commission to you.
Add an affiliate
The code is what a customer types at checkout. Give it to them as it appears here.
Where their login goes. You can add somebody without one, but they will not be able to sign in and see what they have earned.
Letters, digits and dashes. Spaces are closed up.
% of the goods on each order
%
Their login
Send these to now. The password is not stored and cannot be shown again, if it is lost, switch the code off and issue a new one.
Your referrals
Your referrals.
Everything that came in on your code, and what it earned you.
Orders on your code
Commission is owed once an order is paid for. An order that has not been paid yet is shown as pending rather than counted.
Prescribers
Who may write into a compounding pharmacy.
The NPI check is structural. Ten digits with a working check digit means a number could have been issued, not that it was, and not that this person holds it. Confirming it against NPPES is a separate step, recorded against whoever did it, and a login cannot be issued until it has been.
Add a prescriber
Record a licence
Left empty, it is treated as not expiring. A lapsed licence stops working on its own.
New prescription
Write a prescription.
This records a prescription; it is not an electronic signature. It is written under your account and audited, and it is not attested to by a third party the way an e-prescription is.
Patient
Compounded for one individually identified person.
Preparation
Only what the pharmacy you choose actually compounds.
Printed on the label. A preparation dispensed without directions tells the patient nothing.
Authorisation
How much, how many times, and for how long.
Left empty, it is a year from the date written.
Written
Give this code to whoever places the order. It is shown once.
Prescriptions
What you have written.
Prescriptions
Nothing is compounded until somebody says so.
This records a decision; it does not verify a prescription. There is no prescription in this system to check against, the reference below is what was typed at checkout. Check it against the prescription the pharmacy holds before approving.
Prescription
Patient
Patient details are hidden.
This was recorded against your account.
Bundles
Sell more than one thing at a time.
New bundle
Pick at least two products and set one price for the set.
Start from a set
Fills the form below. Nothing is saved until you set a price and press Save, and every field stays editable.
Goes in front of each set name, so they read as yours.
% off sold separately
What is in it
Your bundles
Repeat orders
Offer a discount to customers who want to reorder monthly. They are not charged automatically, the gateway cannot hold a card for that yet, so the checkout promises a reminder at the agreed price, which is a thing you can actually deliver. The agreement and its discount are recorded either way.
Discount codes.
New code
Marketing
What your shoppers actually do.
By product
Sorted by how many people put it in a basket. A product high on this list with nothing in the last column is priced or described wrongly, not unwanted.
Where they came from
What each campaign sold
Only visits that arrived on a tagged link. Revenue is what the customer was charged, before delivery, discounts or anything owed onward, the money that came in because of the campaign, not what was left after it.
Marketing
Every storefront, and each one on its own.
System
Diagnostics.
Full check
Past runs
Sales that failed
Started, never finished
Paid, never sent
Deliveries that didn't reach a supplier
Money taken that wasn't accounted for
Charges that never landed
Cancelling one makes its order unshippable. It moves no money: void or refund it with the processor.
Compounds held twice
Controls that did nothing
Errors
Supplier
Your account.
Orders to fill
Orders with your products on them.
What you supply
Everything you have told us you can fill.
Earnings
What you have earned.
Activity
Get help
Tell us what went wrong.
Your issues
Partner issues
What partners are stuck on.
Customer support
Find an order or a customer.
Clinic commercial view
Clients, orders, and recurring revenue.
Client activity
Orders per week, last 8 weeks
Client list
Your pricing
What you charge.
The file carries every line you may sell, what it costs you, what you charge, what you keep, and which are on your store. Nothing is stored: it is generated when you ask and every download is recorded.
Your words for this product
SourceRX admin
Dashboard.
Partners
PartnerStoreOrdersRevenueProfitMarginMonthlyTrend
Live orders
Watching for new orders…Product performance
What is selling.
Download
A snapshot as CSV. Nothing is stored, the file is generated when you ask for it and every download is recorded in the audit trail.
Orders export one row per line item, with unit cost, unit price, margin, carrier, tracking and the address it shipped to.
ProductManufacturerClassUnitsRevenueProfitStores
Approval-only onboarding
Partner applications.
Application
NewCatalogue
Manufacturers.
Partner network
Partners.
System
Integrations.
Checking…
Send each email to yourself
Goes to you with sample details. One send per minute.
Setting it up
- 1 · API key
- Set
RESEND_API_KEYin Railway, then redeploy - 2 · Domain
- Verify the domain in
EMAIL_FROMwith Resend - 3 · Prove it
- Send a test from this card
Card payments
You can suspend an account. The owner adds, changes and switches on merchant accounts.
Which shops can take cards
Loading…
Manufacturers
Customer emails
Emails.
Sending is not switched on yet, so nothing will go out even when an automation is on here. Your settings are saved and will start working the moment it is.
System
API.
Copy this now. It cannot be shown again.
Paste the raw value. Do not add Bearer in front of it.
Endpoint
-
Keys
What the hub receives
Raw JSON
Partner commerce setup
Partner commerce setup.
No partners exist yet. Approve an application under Applications to create one, then configure it here.
Partner access
Who at this business can sign in. A partner with no login cannot reach the platform at all.
Passwords are generated and shown once. This is a prototype, the account list is stored in the page, so these are not real credentials.
Who supplies them
Read from what this partner sells. Each line is filled by whichever supplier can, chosen per order.
Used only where more than one manufacturer can fill a line: this partner's orders go to the preferred one rather than the cheapest. It does not change what they may sell, and a supplier we cannot reach is still passed over, preferring someone who cannot be told about the order would honour the preference by failing to fill it.
Products selected-
Partner statusApproved
Private pricing
Manufacturer price → SourceRX fee → what this partner pays. Owner-only.
Bulk tier
Dropship tier
Manufacturer price••••
SourceRX fee %
This partner pays-
This partner has no tier on the dropship schedule, so they have no cost basis and nothing to select in their storefront.
The manufacturer price is yours alone. It is not sent to this partner, to any other partner, or to an admin, the API returns it to the owner account only. The fee is what SourceRX takes on top; what the partner charges their own customer is theirs to set and is not recorded here.
Storefront setup
DraftSubmission progress
-
Powered by SourceRX
Product catalog
Products.
Import a price sheet
Adding a few hundred line items through a form is not a workflow anyone follows. Upload your sheet, read the diff, then apply it.
1 · Your sheet
A CSV needs a header row with product and size. Anything with price or tier in its name is read as a price, left to right. category, form and classification are optional, and so are prices.
2 · Read the diff, then write it
Importing the same sheet twice changes nothing the second time, it is matched on product, size and tier, so a spreadsheet can stay the source of truth and be re-imported after every edit.
Category tiles
The picture a shopper sees for each category. Every storefront listing that category shows the same one, so these are yours rather than a partner's. PNG, JPEG or WebP, up to 256 KB.
Lines no supplier declares
Nothing here can be sold. Removing deletes these sizes, their prices and any shop's selection of them, permanently.
System
Apply form.
System
Automations.
Switched on0emails to partners
Available0in the catalog
SendingPausedthrough Resend
Email is not configured on the server, so nothing sends even when an automation is on. Set
RESEND_API_KEY and redeploy, see Integrations.
What each shop sends
System
Team.
Loading…
Add someone
✓ Account created
Give this password. It is shown once. If it is lost, reset it below.
System
Doc links.
Help
How this works.
The short version
1You build a storefront from the products SourceRX has made available to you, and submit it for review.
2You add your clients with a shipping address. That address is where the parcel goes.
3You place an order and choose which client it ships to.
4The manufacturer ships it direct to your client. You never handle stock.
5Your client is emailed the tracking automatically, under your name, your logo and your colour. Replies come to you, not to us. That email carries no pricing.
Tracking appears against the order in your order history as soon as the manufacturer reports it.
Getting help
Email support@sourcerx.us and a person will answer. Include the order reference if it is about an order, it is the fastest way to get a real answer rather than a request for more detail.
Your own customers should contact you, not us. They bought from your store and have never heard of SourceRX, order confirmations and tracking emails already reply to your address, so this happens by itself.
Pricing
The prices you see are what you pay SourceRX, at the tier set for you. What you charge your own customers is entirely yours to decide, set it wherever you like above your cost. We do not record it and nobody else sees it.
Privacy
You cannot see other partners, and no other partner can see you, your clients or your orders. The manufacturer is given the shipping address and the products, and is not told what anything cost.
Your team
Invite colleagues from Settings. Everyone you invite can do everything you can. Nobody can remove their own access, and the last remaining account cannot be removed, that is what stops a business locking itself out.
Full documentation
The technical reference, including the parts written for manufacturers. Opens in a new tab.
Anything about pricing, products or approvals goes to your SourceRX contact rather than the documentation.
Your business
Settings.
Invite a teammate
They get their own sign-in and can do everything you can, build the storefront, place orders and manage clients.
✓ Invitation sent
Give this password. It is shown once and cannot be recovered.
Who can sign in
You cannot remove your own access, and the last remaining account cannot be removed, that is what stops a business locking itself out.
Your website
Developers.
API keys
A secret key is for your server and can read orders with each customer's details. A publishable key can go in your web pages and reads only your catalogue, from the websites you list.
Copy this key now. It is shown once and cannot be shown again.
Try it
Send the key in an Authorization header, from your server. Order reads are logged.
Your products
What your shop sells, with the ids your code uses. Change it in My Store; the API follows straight away.
Webhooks
Where we send order updates. Each one is signed with the endpoint's secret and carries ids and statuses, never customer details.
Your signing secret. Copy it now; it is shown once.
Usage
Requests made with your keys over the last 30 days, and how many were turned away for going over the rate limit.
Your account
Profile.
Details
Your email address and access level are set by an administrator and cannot be changed here.
Authenticator
Patient details on compounded orders need a code from an authenticator app.
Add this secret to your authenticator app, then enter the code it shows.
Shown once. It is not readable again, start over if you lose it.
⚠ This account is set by the environment
The owner login comes from OWNER_EMAIL and OWNER_PASSWORD, and is re-applied on every boot. Editing it here would be undone at the next deploy, so the server refuses the change rather than appearing to accept it. Change those variables in Railway and redeploy.
The upside: if the owner password is ever lost, editing the environment and restarting is the way back in.
Change password
At least 12 characters. Every other browser signed in as you is signed out; this one stays.
SourceRX support
What works, and what doesn't.
The admin side is saved. Accounts, sessions, the product catalog, payment configuration, partners, manufacturers, applications, storefronts, orders and clients are all held in Postgres by the API and survive a reload, a redeploy and a different browser. What remains simulated is listed on the right, those are features that were never built, not data that is being lost.
Real, and saved by the API
Backed by the database. Survives a reload, a redeploy, and a different browser.
✓Sign-in is real authentication. The password is checked against a scrypt hash by the API; the session is a row in the database behind an HttpOnly cookie, so signing out revokes it immediately.
✓Employee and admin accounts. Created from System → Team with a one-time password, and role changes end that person's sessions immediately.
✓Your own profile. Change your name and password from the avatar. Changing a password signs out every other browser and keeps the one you are using.
✓Outbound email through Resend. New accounts and password resets are emailed sign-in details. Both messages can be test-sent to yourself from Settings.
✓The product catalog. Nine categories, products with per-size variants, and a price per size per tier across two independent schedules.
✓Bulk price import. A whole sheet at once, idempotent, with a dry run that reports what would change before anything does.
✓Payment processor configuration. The gateway credential is encrypted before storage and never returned to any page, reads show only its last four digits.
✓Partners, manufacturers and the application queue
✓Partner logins, and a partner's own team. Real accounts bound to the partner record, emailed their sign-in details. A partner invites its own staff from its settings without an administrator; every teammate is a peer, nobody can remove themselves, and the last account that can sign in cannot be removed. They see only that partner, not the directory, the catalog, or anyone else's orders and clients. Suspending the partner locks the whole team out immediately; deleting it removes them.
✓Public application form → review queue → approve, which creates the partner
✓Product availability by partner type
✓An audit trail of every access and money-configuration change
✓Public storefronts. An approved partner's store is live at its own address, showing the products they chose at the prices they set, under their name, logo and colour, with no mention of SourceRX anywhere on it.
✓A basket and a checkout. A customer can browse, add, and place an order with a delivery address. Prices are looked up server-side, never taken from the page, and a product another partner sells is not purchasable through this one.
✓Payments are connected. The processor authenticates, a payment is recorded against an order, and a signed webhook settles it. A forged one does not, an unsigned or wrongly-signed notification leaves the payment pending.
✓Nothing ships until the money arrives. An order is released to a manufacturer by a settled payment, not by anyone filling in a form, and a redelivered notification does not send a second parcel.
✓Manufacturer catalogs are read hourly. A supplier publishes a URL; we fetch it, match it to the shared catalog, and record what they can fill and how much they hold. A failed read is recorded against them rather than mistaken for silence.
✓Orders reach the manufacturer, tracking comes back. Each line goes to whoever can actually supply it, under their own code, with no pricing and no partner identity attached. They report the carrier and tracking number back.
✓The customer is emailed, as the partner. Order confirmation on settlement and tracking on despatch, carrying the partner's name, logo and colour, replying to the partner's address.
✓A merchant account per partner. A customer's bank statement names the shop they bought from, not the platform underneath it.
Also real, and saved
The partner workspace. These moved out of browser memory and into the database.
✓Storefront build → submit → approve or request changes. The selection, the DBA and the review state all persist.
✓Ordering and order history. Each line records what the unit cost and what it sold for at the moment it was placed, so changing a markup later does not rewrite an old order's margin.
✓Clients. Name, stage, spend and recurring revenue.
✓Pricing tiers. A partner holds one tier per schedule, and their cost basis is the catalog price at that tier.
✓Markup and derived partner pricing. Saved when the pricing is activated.
✓Every filter, metric and chart, real arithmetic over real stored data
✓Admin viewing any partner's workspace
Cost basis and markup are still sent to the browser for any signed-in admin, so they are visible in devtools to anyone with an admin session. They are no longer visible to a signed-out visitor.
Not built
Kept honest deliberately. Everything above this line works against real services; everything below does not exist yet, and is listed so nobody discovers it at an inconvenient moment.
!Checkout does not hand off to the payment page. The processor is connected and answering, the ledger records payments, and a settled payment releases an order, but the storefront still stops at "reserved" instead of sending the customer to pay. Until that is joined up, no card is charged. It is the one thing standing between the platform and a real transaction.
!Products have no images or descriptions. A storefront lists a compound, a size and a price. There is nowhere to put a photograph or a paragraph, so a customer is buying from a bare line item.
!Orders a partner places themselves send no confirmation. A customer buying through a storefront is emailed when their payment settles. An order a partner enters in their own workspace owes nothing at the point of ordering, never settles, and so triggers nothing.
!Refunds are recorded, not initiated. When the processor reports a refund we write it against the payment and the order. There is no button here that asks them to make one.
!Storefronts have no custom domains. A partner's store lives at a path on this domain, not at one of their own.