SerialFlow is in beta. This page says exactly what that means: what you get, what it costs, what is not built yet, and what you can expect from us when something goes wrong. Nothing here is hidden in the terms; the terms point to this page.
1. What beta means here
Beta means the product is complete enough to run a business on, and we run our own on it every day: the warehouse SerialFlow was built for receives, grades, lists, ships and returns its stock through the same code you are using. It also means the product is still changing week to week, some features are new enough that we are still finding their edges, and the parts named in section 4 are not built at all.
Concretely, during the beta you should expect: features to be added and refined without notice; a known issues list that is honest and current; a changelog you can read; and a fix, or a straight answer about when to expect one, for anything you report. You should not expect: a feature that is on the out-of-scope list, an uptime guarantee with a number attached, or a support promise larger than the one in section 5.
The stages, so the word means the same thing to both of us:
Stage
What is true of it
Beta (now)
Complete enough to run on. Free. Caps apply. Changing weekly. Support by email, by severity. Your data is yours and exportable throughout.
General availability
Priced plans published and confirmed to you by email before anything is charged. Exit criteria in section 6 all met. A larger support promise and a published availability target.
2. The offer: free, no card, capped diagnostics
Free. There is no subscription fee during the beta, and every feature that exists is included. There is one plan, and it is the beta plan.
No card. Signing up asks for a workspace name, an email address and a password. You may add a payment method later through the billing page if you want one on file; it is not charged during the beta.
One metered service, with a cap. Device diagnostics (IMEI, blacklist and carrier checks) cost us money on every check, including a failed one, so each workspace has a cap of [diagnostics checks per month]. The workspace shows the count and the cost basis of every check; when the cap is reached, diagnostics pause until the next period and nothing else stops. Nothing else is metered.
Postage is never ours. Shipping labels are bought through your own ShipStation or carrier account, under your own billing there, and that account has to be funded before the first label prints. SerialFlow never holds postage money and never charges you for a label.
An end date. The beta runs until [beta end date]. Section 6 says what happens then, and the terms guarantee notice by email before any fee starts.
3. What is complete
Everything below is built, in daily use, and covered by the user guide:
Serialized units (IMEI and serial, grade, cosmetic condition, defects, cost, bin) beside bulk stock with a quantity, an average cost and a reorder point.
Purchase orders with receiving by scan, cost layers, freight into cost of goods, and supplier payments.
Sales orders, picking, and shipping through ShipStation or ShipEngine, with rate shopping, labels, voids, manifests and customs paperwork.
Returns (RMAs) with receive-back to stock and the financial reversal.
A double-entry financial ledger, profit to the single unit, and an analytics hub with export.
The eBay integration: listings, orders, tracking push-back, and multi-variation parents.
A wholesale buyer portal you operate under your own name, with buyer approval, offers and lot listings.
Label printing (thermal and sheet) with a visual template editor.
Device diagnostics with a per-workspace meter.
A team with capabilities per person, invitations, and revocation that takes effect within a minute.
Import of customers, vendors, stock with cost and open orders from a spreadsheet, with a dry run and a record of what changed.
4. What is out of scope, in writing
These are not on the roadmap for the beta, and a workspace that needs one of them today should not sign up expecting it. We would rather say so here than have you find out on a Tuesday afternoon.
A repair and refurbishment pipeline. There is no work-order, parts-consumption or technician-queue module. Repairs are recorded today as a cost line on the unit and a status change.
Sales channels beyond eBay. Swappa, Back Market, Reebelo, Walmart, WooCommerce and Shopify are not connected. Amazon exists as a channel name and a plan, not as a live connection. Orders from another channel are entered as direct sales or imported from a spreadsheet.
An accounting connector. There is no QuickBooks or Xero sync. The ledger, the profit and loss and every report export to CSV, and that is how figures reach your books today.
Buyer-initiated returns. A buyer on your portal cannot open a return themselves. Returns are raised by your staff in the RMA module.
Enforced two-factor sign-in. Sign-in is email and password today. An optional authenticator app per person is planned during the beta; requiring it for a whole workspace comes after.
Smaller gaps, and every defect we know about, are on the known issues page, which is updated as they are found and fixed.
5. The support promise, by severity
Support is by email at support@serialflowinventory.com, or through Send feedback in the app’s help menu, which attaches the page and the workspace for you. Hours: [support hours and timezone]. The promise is modest and it is real:
Severity
What it covers
First reply
Then
1. Down or wrong
The service is unreachable, or a stock count, a cost or a sale is recorded wrongly.
Within [4 business hours]
Worked continuously until resolved; updates at least daily.
2. Blocked
A feature you rely on does not work and there is no workaround.
Within [1 business day]
A fix or a dated plan for one within three business days.
3. Everything else
A question, a request, a cosmetic defect, something with a workaround.
Within [2 business days]
Answered, or logged with a note in the changelog when it ships.
Incidents and planned maintenance are published on the status page linked from the help menu, and a migration from another system gets a named person for the move: ask, and one is assigned.
6. How the beta ends
The beta ends when all of the following are true, and not before:
Priced plans are published on the pricing page, and every beta workspace has been told by email which plan it is on and what it will cost, at least [notice period, for example 30 days] before the first charge.
The known issues page holds no open severity 1 or severity 2 item.
A whole-workspace export is available from Settings without asking us.
The support promise above has been met for the preceding [period, for example 60 days].
On the end date, the workspace continues on the plan you were told about. If you would rather leave, you export your data and close the workspace before then, as the terms describe, and nothing is charged.
7. What we ask of you
Tell us when something is wrong, with the page you were on. The feedback control does the attaching.
Read the known issues page before relying on a feature it names.
Keep your own records where the law requires them; check the figures the service produces before you file them.
Let us talk to you now and then about how you use it. That is where the next feature comes from.