How the options compare
Four ways to run a spine distributorship, on the outside and on the inside.
A spine distributorship that has outgrown the spreadsheet has three places to go: a generic medical device distributor app on a shared cloud, a general-purpose ERP provisioned by an implementation partner, or FieldRep Ops. In a demo they look more alike every year. Here they are side by side, kinds of system rather than named products, in two bands: what a demo shows, and what it does not.
Of the four, two give your spine distributorship its own database: a provisioned ERP and FieldRep Ops. The apps keep every customer in one shared database, where one incident is every customer's incident, and the duty to notify patients falls on each distributorship. What separates the ERP from FieldRep Ops is months of configuration and the bill that comes with it.
| A bookkeeper and spreadsheetsThe status quo: accounting software for the books, a workbook per rep, the owner's evenings for month end. | A generic medical device distributor appA phone-first app for any device line, sold per rep seat or flat per month, running on one cloud the vendor shares across all its customers. | A provisioned ERPA general-purpose business system configured for your spine distributorship by an implementation partner, with add-ons for what it lacks. | FieldRep Opsthis oneOne system built for the whole spine distributorship, from the signed delivery order to the owner's month end, in your own private environment. | |
|---|---|---|---|---|
| On the outside | What a demo shows. Here the apps, a provisioned ERP and FieldRep Ops look convincingly similar. | |||
| ✓by hand | ~ | ✓configured | ✓ | |
|
Why it matters: a spine distributorship rarely pays two reps the same way, and the best-compensated reps in the hospital read every line of their statement. The agreement is where month end goes right or wrong. BookkeeperDone by hand, painstakingly: a complex workbook for each rep, with every surgeon rate, override and coverage fee carried in someone's head and rebuilt each month.
Distributor appCommission tracking, or at best a rate for each rep by manufacturer with an override. A rate for one surgeon or one hospital, a choice of paying on the sale or on the commission, a set fee for covering a case: not usually in it.
Provisioned ERPPossible with a commission add-on, once the implementation partner has built each rep's plan. A change to an agreement usually goes back to the partner.
FieldRep OpsEach rep on an agreement of their own, built line by line: paid on the sale, on the commission or as a flat amount; a rate by surgeon, hospital or manufacturer; overrides; assisted cases; à la carte coverage fees by procedure; hospital-owned stock. Leadership sets it once and every signed order is paid under it. No two rep agreements are the same.
| ||||
| ✗ | ✓ | ✓ | ✓ | |
BookkeeperOne accounting login and a shared workbook. Who changed what is anyone's guess.
Distributor appA seat per rep, or role-based access up to a set number of users inside the fee.
Provisioned ERPNamed users with roles, each one licensed.
FieldRep OpsUnlimited users. Reps see their own cases and pay, leadership sees everything, the office works the queues.
| ||||
| ✗ | ✓ | ✓configured | ✓ | |
BookkeeperA photo of the sheet, texted to the office.
Distributor appBuilt for it. Native phone apps in most.
Provisioned ERPMobile apps exist for the cloud suites; the partner configures what a rep sees.
FieldRep OpsThe delivery order, signatures, tray check-in and photos all run on the phone.
| ||||
| ✗ | ✓ | ✓configured | ✓ | |
BookkeeperPaper, or a photo of paper, re-keyed later.
Distributor appThis is what the apps are for: signed at case close, priced from the facility contract.
Provisioned ERPNot a document any ERP ships with. The partner builds it as custom work, priced separately.
FieldRep OpsOn the phone, with signatures and hospital-specific pricing. The implants at every level and the biologic on one numbered order that bills five figures, and is never rewritten.
| ||||
| ~ | ✓ | ✓ | ✓ | |
BookkeeperThe accounting software can raise one. Chasing the hospital's is a memory task.
Distributor appPO entry, a view of open orders, restock orders to the manufacturer. The hospital's PO for the case is typed in; nothing reminds you when one stalls.
Provisioned ERPPurchasing is core. It tracks the PO you create and does not chase the hospital's.
FieldRep OpsEvery delivery order carries its PO and payment state. Follow-ups go out on schedule, and a daily digest lists what is still owed. On a spine case, the PO that stalls is a five-figure one. The PO that never came.
| ||||
| ✗ | ✓ | ✓configured | ✓ | |
BookkeeperNobody has a ledger. Trays go missing at hospitals.
Distributor appInventory levels and locations; loaner check-out and check-in in the fuller apps.
Provisioned ERPInventory is core. Consignment shelves and loaner sets are a configuration or an add-on.
FieldRep OpsTrays checked in and out, photos at check-in, what was short logged on arrival, due dates with a daily reminder.
| ||||
| ✗ | ~ | ✓configured | ✓ | |
BookkeeperTracking numbers in email.
Distributor appLabels and tracking in some; others mark a tray "in transit" with no carrier behind it.
Provisioned ERPThrough a carrier add-on.
FieldRep OpsCarrier tracking on the delivery order, with the destination checked against the ship-to.
| ||||
| ~ | ✓ | ✓ | ✓ | |
BookkeeperWhatever the owner builds in the workbook.
Distributor appRevenue, margin, rep and facility reporting in the fuller apps; case counts in the simpler ones.
Provisioned ERPThe deepest reporting of the four, once someone has built the reports.
FieldRep OpsDashboard, ledger, month end and the owner's P&L, from the same records the statements are built on.
| ||||
| ✗ | ✗ | ✓configured | ✓ | |
BookkeeperTotals are checked against deposits. Lines are not.
Distributor appNot offered by any app in this category. The commission is computed from a rate table before the manufacturer has paid.
Provisioned ERPNot native anywhere. The partner builds it as custom work.
FieldRep OpsBring in the statement as it came, as a file or pasted rows, and it never leaves your browser. Each line is matched to its delivery order by purchase order number; you accept what matches, the dispute for the rest is drafted with the send record attached, and each line is marked paid when the money lands. How to work a short statement.
| ||||
| ✓ | ~ | ✓ | ✓ | |
BookkeeperThis is the job: rebuilt by hand each month from the workbook, and every rebuild drifts.
Distributor appNo accounting module. Exports a spreadsheet to your bookkeeper, who still builds the month from it.
Provisioned ERPThe general ledger is the product; the books live inside it and your CPA works from there.
FieldRep OpsYou still keep your accounting software and your CPA; this is not accounting software. The difference is the month close: the month is closed in the system against the signed orders, checked, and what reaches the books is that closed month, not rows for someone to assemble and check by hand. The export carries case numbers, never a patient identifier.
| ||||
| On the inside | What a demo does not show: security, monitoring, reliability, integrity. This is where a provisioned ERP and FieldRep Ops are alike, and the others are not. | |||
| ~ | ✗ | ✓ | ✓ | |
|
Why it matters: in a shared database, one incident is every customer's incident at once, and the duty to notify patients under state breach laws is yours either way. The record systems large hospitals run typically give each health system its own. The apps in this category give every customer the same one. BookkeeperNo other customer is in your files. Nobody is guarding them either.
Distributor appOne shared database for every customer, kept apart by a policy on each row that no customer can inspect. Whether and how is rarely published.
Provisioned ERPYours. Installed or hosted for your distributorship alone; that is what provisioned means.
FieldRep OpsOne private environment per distributorship: its own project, database, storage, encryption key and identity.
| ||||
| ✗ | ✗ | ~ | ✓ | |
|
Why it matters: the real risk is a phished rep, or a password reused from a phone game that was breached. In a shared database that rep can be anyone's, anywhere in the country. In your own environment, only yours, and a reused password alone does not get in. BookkeeperEmail attachments and a shared drive.
Distributor appYour sign-in is an email and password the vendor stores. Files are commonly served by links that anyone holding can open until they expire. Some apps hold your manufacturer portal password and log in as you.
Provisioned ERPCompany sign-in is available in the cloud suites; document links usually sit behind it.
FieldRep OpsYou sign in with your own Google Workspace, two-step required, so a reused or phished password alone does not get in. We store no passwords. There are no shareable links: every file read is checked against who is asking.
| ||||
| ✗ | ✗ | ✗ | ✓ | |
|
Why it matters: less held is less to lose, and most state breach laws treat encrypted data differently from plain text. BookkeeperWhatever the rep wrote on the sheet, photographed, and emailed.
Distributor appA free-text case identifier stored as typed. Nothing published on what is held or for how long.
Provisioned ERPNot designed for it. Whatever gets typed into a notes field stays there.
FieldRep OpsThe hospital's identifier and the case date, nothing else. Encrypted with a separately held key, deleted 90 days after the case is paid or voided.
| ||||
| ✗ | ✗ | ✓ | ✓ | |
|
Why it matters: an outage is news you want from the vendor's status page, not from a rep standing in the OR. BookkeeperNobody is watching.
Distributor appNot published. Few publish a status page, and the terms usually say uninterrupted operation is not guaranteed.
Provisioned ERPThe cloud suites run an operations centre and a service-health page. A partner-hosted system depends on the partner.
FieldRep OpsMonitoring and alerting built to data-center standards, watched around the clock. A public status page at status.fieldrepops.com shows current and historical uptime.
| ||||
| ✗ | ✗ | ✓ | ✓ | |
|
Why it matters: a backup nobody has restored is a hope. Ask any vendor when they last restored one. BookkeeperDepends on whose laptop it was.
Distributor appNo backup, recovery or uptime statement published.
Provisioned ERPBackups and recovery under the enterprise contract. Restores go through support.
FieldRep OpsNightly backups to a separate project in another US region, point-in-time recovery, and a monthly restore drill that actually restores.
| ||||
| ✗ | ✗ | ✓ | ✓ | |
|
Why it matters: the money mistakes that get past testing are the ones where every line is right and the total is wrong. On a case that bills five figures, that is real money. A system that re-adds its own totals against the signed orders finds it before a rep's statement or a manufacturer's audit does. BookkeeperThe check is a person re-adding the spreadsheet, and the cell they fix is overwritten in place.
Distributor appNothing published on how totals are verified, or how a correction to a signed document works.
Provisioned ERPA general ledger balances itself and posted entries are reversed, not edited. What the partner built on top is checked by the partner.
FieldRep OpsFifteen reconciliation checks compare every total to the signed orders it came from, before every release and every week in production. A signed order is never edited quietly: a correction is recorded field by field with the old value, the new value and the reason, the history stays, and the document number is never rewritten.
| ||||
| ✗ | ~ | ✓ | ✓ | |
|
Why it matters: when something goes wrong, what you can rely on is what was written down before it did. BookkeeperYou.
Distributor appTerms and a privacy policy, where published. Liability capped at a year's fees, insurance not stated, getting your data out not stated.
Provisioned ERPA published contract, enterprise notice terms and the vendor's insurance. You are inside a multi-year term and exporting is a project.
FieldRep OpsA signed agreement and Data Protection Addendum, incident notice in writing within five days, cyber and errors-and-omissions cover, and a security page where every claim can be checked. Month to month, data exported on request.
| ||||
| ✗ | ✗ | ~ | ✓ | |
|
Why it matters: sooner or later a hospital's IT department asks what system its purchase orders and patient identifiers are passing through. The answer that satisfies them is a document you can hand over, not a call you have to make. BookkeeperNothing to hand over. The questionnaire lands on the owner's desk.
Distributor appA security page on the website at most. A statement covering where the data sits, who can reach it, how it is backed up and what happens after a breach is not published by the apps in this category.
Provisioned ERPThe cloud suites publish security documents and audit reports for the vendor's own platform. They describe the vendor's cloud, not what your partner built on it or who in your distributorship can reach what.
FieldRep OpsLeadership downloads the Data Handling & Security Summary from the Compliance area as a PDF, written for hospital security reviewers and counsel: what is held about patients and for how long, where the data lives, who can get in, encryption, backups and recovery, and the date those controls were last verified against the live infrastructure. Security questionnaires are answered in writing, and the Data Protection Addendum is provided before you sign.
| ||||
The three comparison columns are kinds of system, not named products. Their marks are our reading of what those kinds of system publish and show as of November 2026; if you know one that does better on a row, we would like to hear it. The FieldRep Ops column is checkable against the security page and a walkthrough.
Why this matters to you
The outside of these systems is converging. A charge sheet signed on a phone, a tray ledger, a commission number: within a year every app in this market will show you those in a demo. They are not what you are choosing between.
What you are choosing is where your money record and your hospitals' patient identifiers live, who can reach them, and what happens on the day something goes wrong: a breach, an outage on a surgery morning, a lost laptop, a hospital's security review, a manufacturer disputing a statement. The breach is not a hacker in a hoodie. It is a rep who clicks a convincing email, or who used the same password for the app and for a phone game that was breached last year. In a shared-cloud app that rep does not have to be yours: every rep at every customer signs into the same database, held apart from your records by a policy you cannot inspect. When it goes wrong, the notice to your patients, and in many states to the attorney general, goes out under your distributorship's name, not the vendor's. Everything else a demo does not show is the other days: the server down on a surgery morning, the backup never once restored, the hospital's IT asking for a security statement, the manufacturer asking for the original.
Two of the four systems are built for those days: a provisioned ERP and FieldRep Ops. The ERP gets there with an implementation partner and months of configuration before the first live month, and it still does not know what a delivery order or a manufacturer statement is until someone builds that. FieldRep Ops is built around those two documents, for spine, where one signed order can bill what another distributorship bills in a week, in a private environment that is yours alone, running in days.
The shared-cloud apps are cheaper on the sticker, and one may look fine on the outside, especially from a rep's seat. For the distributorship, the price you are not shown is the one that arrives with the incident: your records in the same database as every other customer's, the duty to notify each patient's home state landing on you, and nothing published about who stands behind the vendor when it does. And whatever the paperwork between you, the vendor and the hospital says, it was your hospital's data that leaked out of an app you chose. You report it. Then you explain it to the hospital. You do not keep that hospital. A rep can move to another territory. The distributorship that chose the app cannot.
Ask any vendor five questions, and ask them in writing
- Is my database my own, or shared with your other customers?
- Do you hold any of my passwords? And can anyone who gets hold of a link to one of my files open it, without signing in?
- Is the patient identifier encrypted, and who holds the key?
- When did you last restore a backup, and where is your status page?
- What do you commit to in writing if something goes wrong, and what insurance stands behind it?
Every answer for FieldRep Ops is on our security page, where each claim can be checked.
What it does, page by page
One page per thing the system does for a spine distributorship, each checked against the product as it runs today.
Founding distributors
We are taking on a small number of founding spine distributors now, who use FieldRep Ops free while it proves itself on their books and know the price before they start. One private environment per distributorship; nothing shared with anyone.