Customer
Queue position, quote decisions, history, and loyalty in the customer's pocket.
Preparing your workspace
The workshop, the parts room, the counter, the staff roster, and the owner’s numbers, for Philippine motorcycle shops. One system where there were five, and every figure on it opens the work that produced it.
₱0 during the controlled pilot. Per branch pricing starts only once MotoCoreHQ runs your day.
Recording approved scope, quality checks, parts usage, labour minutes, quote versions, photo evidence.
Service records
1,284 records · updated 10:52
Waiting
12+2 today
In progress
73 bays
Ready
6awaiting pickup
Collected
| Reference | Customer | Motorcycle | Status | Approved | Updated |
|---|---|---|---|---|---|
| SR-1024 | Ana Santos | Honda Click 160 | Pending review | ₱4,850 | 10:18 |
| MC-2026-0481 | Miguel Reyes | Yamaha NMAX | Inspecting | ₱2,120 | 10:52 |
| MC-2026-0476 | Jo Ramos | Suzuki Raider 150 | Ready for pickup | ₱6,400 | 09:41 |
| MC-2026-0470 | Cess Villamor | Honda TMX 125 | Awaiting approval | ₱1,980 | 09:22 |
| SR-1019 | Lito Bautista | Kawasaki Barako | Intake rejected | Not billed | 09:05 |
Branch workspace, shown with sample data.
Customer, manager, mechanic, cashier, owner
One connected ledger, not seven spreadsheets
Today's branch QR, or a manager at the counter
Priced per branch only once it runs your day
From the shutter going up to the bike rolling out: a customer, a mechanic, the counter, the roster, and the owner's numbers, drawn as fifteen sheets of the blueprint a shop already works from. Narrated, with captions on screen.
Every morning, a shop like yours rolls up the shutter. The first bikes are already waiting. And the day starts the way it always has.
Most shops run on paper slips, chat threads, and memory. And it works. Until someone asks a question.
Who approved this repair? Where did that part go? Who was actually on shift on Tuesday? Nobody wrote it down. Or three people wrote three different versions.
MotoCoreHQ puts the whole shop on one record. Intake, quotes, parts, cash, staff, and the owner's numbers.
A customer scans the branch QR at the door and gets a queue number. The quote lands on their phone, and they approve it right there.
The manager accepts the job and assigns it. The mechanic works the checklist, shoots the evidence, and pulls parts straight from branch stock.
Every part lives on one ledger: scanned, reserved against a job, counted. Running low? A restock request becomes a purchase order, and stock moves between branches on record.
At the counter, payment, loyalty points and the receipt happen in one step. And the bike rolls out, released.
Staff punch in with a code and a photo. Timesheets, leave, and the payroll export build themselves.
Come payday, the hours are already there: worked, overtime, late, straight from the punches. A pay ladder sets each mechanic's class, the period closes, and the payable share exports as a payroll CSV. MotoCoreHQ prepares the numbers. Your payroll releases the pay.
And the owner sees every branch on one dashboard, where every figure opens the job behind it.
Then the questions every owner asks. Is today making money? Net sales, margin, and what is committed but not collected. Who is slipping? Quotes waiting, jobs past their ready by time, bikes not collected. Where is the money going? Expenses with budgets, and a trail of who did what.
And they come back. Reminders, a service due call list, loyalty points, and a booking for the next visit.
Purchase orders, branch transfers, engine builds with deposits, expenses, offline drafts, printable estimates, exports. It is all in there.
₱0 during the controlled pilot, then ₱2,490 per branch per month. Multi-branch is custom. Book a demo.
It works until someone asks, a week later, who approved this and where the part came from.
Not features. The specific disputes that cost a service shop money, and the mechanism that ends each one.
The customer approves line by line, and a correction writes a new version rather than overwriting the old one.
Work outside the approved scope stays blocked, not flagged.
Revenue, rankings, and exceptions all drill back to the service record that produced them.
Reconciles to the source job, down to a single line on a receipt.
Reservations, job usage, corrections, transfers, deliveries, and counter sales all write to the same place.
One ledger, six movement types, no second spreadsheet.
Enrolled devices keep checklists, labor, and diagnoses working through an outage, and surface conflicts for review.
Approvals, prices, payments, refunds, and release stay confirmed by the server.
The gates are not friction added on top. They are the reason the record can still be trusted a month later, when a customer asks who approved a ₱4,850 repair.
The customer scans the QR issued for that branch on that service day, or a manager records an assisted intake at the counter.
No queue number until a manager accepts
Checklists, measured values, and photo evidence attach to the job. The customer approves or declines each line.
Unapproved lines cannot be worked or billed
The cashier collects, the manager passes quality control, inventory and loyalty post, and the motorcycle is handed back.
Nothing here can be completed from a device that is offline.
A shop runs on trust. Trust runs on records nobody had to remember to write.
Each role sees what the next decision needs, while every handoff stays on the same record, inside the same branch.
Queue position, quote decisions, history, and loyalty in the customer's pocket.
Reviews first, then queue order, assignment, and release readiness.
One job at a time, with checks, photos, and parts kept in context.
Balances, payment history, and a release the checklist has to clear first.
Branch comparisons that drill back to the records behind them.
Explore a product workspace
Customer portal
Follow active service, answer a quote, review evidence, and come back to the full history from one portal built for a phone.
Review 3 recommended items before the workshop continues.
Representative product preview with sample data.
Running in the build today rather than sitting on a roadmap. A branch gets all of it on day one.
Offline on an enrolled branch device covers drafts, checklists, labour, and diagnosis. Approvals, prices, payments, refunds, loyalty redemption, and final release are always confirmed by the server. MotoCoreHQ is not an accounting or ERP replacement.
You pay once MotoCoreHQ runs your daily operations, not before.
₱0
during the controlled pilot
One branch running the full service journey while workflows are validated.
₱2,490
per branch / month
Everything a single shop needs to run daily operations without paper.
Custom
for shop networks
Shared customer identity and controlled operations across branches.
Introductory pricing in Philippine pesos. Final plans are confirmed after the pilot exit review.
It connects motorcycle repair intake, job orders, mechanic work, estimates, parts, payments, customer updates, and reporting in one operating system. MotoCoreHQ keeps each decision tied to the same traceable service record.
Shops running one branch, and networks growing into several. Each role gets its own workspace for customers, branch managers, mechanics, cashiers, and owners, and nobody sees information outside their scope.
Yes. Parts receipts, reservations, job usage, transfers, corrections, deliveries against a purchase order, and counter sales all update the same immutable branch inventory ledger.
Customers review itemized quote versions, approve or decline each added service, and follow queue and job updates from the mobile portal. Approved scope, evidence, receipts, and service history stay connected to their motorcycle.
New service requests start at a physical branch. Customers scan the branch QR issued for that day, or a manager records an assisted intake on an enrolled branch device. A manager still verifies arrival before anything enters the queue.
Yes. Shops configure booking against the capacity they actually have for engine builds, Dyno or ECU remap work, and preventive maintenance, including deposits, date changes, and closures.
Enrolled branch devices keep eligible checklists, labor entries, diagnoses, evidence, and assisted intake drafts until connectivity returns, and conflicts are surfaced for explicit review rather than merged silently. Approvals, prices, payments, refunds, loyalty redemption, and final release are always confirmed by the server.
No. MotoCoreHQ manages motorcycle service operations, inventory movements, payments, receipts, and operational reporting, but it is not a full accounting or ERP replacement.
Tell us about the shop and we will walk through verified intake, the workshop flow, quotes and approvals, and owner reporting. A working session, not a slide deck.
Pilot access is free while operations are validated with real branches.