In ApplianceOps the call is the invoice — no re-keying a ticket into a separate billing app. Invoice per machine, take a card on your own Stripe account, send a pay-link or PayPal, and capture the signature with zero bars in the driveway. Built so a dropped connection can never lose collected money.
// Full offline invoicing + signatures · card fees are yours, not ours — the platform takes no cut
A generic invoice is one flat list. A repair call is a fridge and a dryer, each with its own service fee, parts, and labor rate. ApplianceOps bills it the way it really happens.
Each machine on the call gets its own block — service-call fee, model and serial, labor rate, parts, and services — so a two-appliance visit reads clean and prices right.
Charge a card three ways — hosted checkout, a pay-by-card link, or record it manually — all landing on your own Stripe Standard account. You own the fees and chargebacks; the platform takes no cut.
Text or email a pay-by-card link, or drop a PayPal.me link. The public invoice can let the customer pay now, with Affirm and Klarna passing through on your account.
Capture the customer's signature (and a driver's, on a delivery) plus before-and-after photos, right on the phone — attached to the call for the callback down the road.
Flat-rate services, parts with cost and markup, delivery, haul-away, shipping, a late-fee line, and flat or percentage discounts. Mark lines "quoted" for an estimate; Accept commits it.
Gapless, immutable invoice numbers and three PDFs — Service, Machine, Parts — plus NO-DOC and no-warranty print flags. Send by SMS, email, link, or QR.
The same call that was booked becomes the invoice, the payment, and the receipt — money-safe even if the connection drops.
Building the invoice, recording a cash or check payment, and capturing the signature all work fully offline. The queued rows land when you're back on signal — engineered so collected money is never lost.
Actually running a card through Stripe needs a connection. With no signal you can still record the payment method and total, present a QR to pay, or send a pay-link the customer taps later.
Cards settle to your own Stripe Standard account — you keep the processing relationship, the fees, and the chargebacks. ApplianceOps doesn't take an app fee on your money.
Invoicing software is easy to build and hard to make trustworthy. These are the parts you only appreciate the day something goes wrong.
There's no booking that becomes a job that becomes an invoice, with three chances to drift apart. It's a single record from the first phone call to paid — which is why nothing has to be copied forward, and why the total on the truck is the total in the office.
The integrity checks sit in Postgres, not just in the screen you're looking at. A phone that's been offline for a week and syncs a stale total can't write a number that doesn't add up — the database refuses it, rather than the app politely accepting it.
Fix a mistyped payment and the history stays intact: the correction is recorded as a reversing entry, not an edit that quietly rewrites what happened. When you or a bookkeeper look back in March, the story is still there.
Take a deposit to hold a machine or secure a job, and the balance comes off the same invoice when the work is done. No reconciling a deposit against a separate ticket by hand.
Refunds are issued against the original payment on the invoice itself, so what went out is tied to what came in instead of living in a payment processor you have to go and reconcile separately.
A payment that arrives without a matching invoice doesn't vanish into a report nobody opens — it gets surfaced so somebody can attach it. Unmatched money is how a shop ends a quarter certain it billed more than the bank agrees with.
The one that understands a repair call. Most tools model a job, then a separate invoice, and make you carry information between them. Here the call is the invoice, with a block per appliance so a two-machine visit bills correctly instead of collapsing into one line.
Build the invoice, capture the signature, complete the job — all offline, syncing when you're back. Charging a card needs a connection, because the card network is online by definition. Anyone claiming otherwise is queuing the charge and hoping.
No. Cards run on your own Stripe account at your rate. Payments are a feature here, not a revenue share.
Yes — send the invoice and they pay from their own phone. Or take the card on site, or use PayPal. All three land on the same record.
Corrections are reversing entries, not edits, so the audit trail survives. And refunds are issued against the original payment on the invoice itself.
Completed invoices push to QuickBooks Online — one at a time, all at once, or on a nightly run. No re-keying.
Per-machine invoicing, payments on your own account, and full offline signatures are in the base plan. From $35/mo plus $15 per extra seat.
// Related: QuickBooks sync · Parts tracking · All features