“Walk-in sales go in a notebook. The notebook goes nowhere.”
If this sounds like your week
A customer walks in, you jot specs on paper, take payment or a deposit — and the notebook page never reliably becomes production work.
Online orders have a system; counter sales have handwriting someone must remember to transcribe.
Purchasing does not see walk-ins. Production finds out late. Follow-up never happens because the sale never entered the pipeline.
You trust the notebook until the page is lost, illegible, or buried under yesterday’s list.
What is actually going wrong
Walk-in intake is separate from the job system — capture happens on paper, execution happens elsewhere.
There is no mandatory path from counter sale to job, task, or ledger.
Staff treat walk-ins as informal — until the informal sale is the one that ships late.
Dual processes (online vs counter) mean dual failure modes.
This is not a recording problem. It is an intake gap — the sale is captured, then stranded outside the system everything else runs on.
Count yours
- Count walk-ins last month — how many reached production the same day without someone chasing the notebook?
- Add one walk-in that never shipped because the page was missed — revenue and trust lost.
- Add re-entry time typing counter sales into the store or spreadsheet after the fact.
What it looks like when this stops
Orders and jobs created in CoreXBiz — including counter and phone sales entered as estimates or orders — follow the same Workflow path as WooCommerce sales once recorded.
CoreX Products defines what you sell with specs and stages — walk-in work can start from the same product definitions as online lines instead of blank notebook rows.
Quoting & Invoicing supports quotes, invoices, and payments connected to the job — a counter sale can become billable work with a receipt, not only a scribble.
WooCommerce remains the path for online sales today; walk-in intake is operational entry inside CoreXBiz — not a claim that every physical POS is replaced on day one, but that counter sales do not need a separate dead-end notebook once entered.
Where CoreXBiz connects
This problem maps to connected modules inside CoreXBiz — not a single feature bolted on.
- Workflow / Jobs Available
- Quoting & Invoicing Available
- CoreX Products Available
Realistic scenario
Composite example for illustration — not a named customer account.
A frame shop logged walk-ins in a spiral notebook while web orders flowed to production automatically. Staff now enter counter sales as orders in CoreXBiz at the desk — production sees the same job board for walk-in and online work once the sale is recorded.
Composite illustration — not a named customer account.
Common questions
- Do I need a POS terminal?
- Not necessarily. Many shops enter walk-in sales directly as orders or estimates in CoreXBiz. A dedicated POS may remain for card present workflows — evaluate what you use today versus creating the job record inside CoreXBiz at the counter.
- Will walk-ins sync with WooCommerce automatically?
- Walk-ins entered inside CoreXBiz become operational jobs directly. They are not required to pass through WooCommerce unless that is how you choose to record them. Online WooCommerce integration and in-person entry can coexist.
- What about quick counter transactions?
- Speed depends on product templates and trained staff — configured products reduce typing. Truly ad-hoc counter work still needs entry; the goal is entry once into the job system, not transcription later from a notebook.