All features
Guest check-in & QR scanning
Know who arrived before departure time starts asking the question.
DockFlow keeps the guest record, mobile pass, QR validation and live check-in state connected to the booking and the operation the guest is here to join.
QR validation
Live arrival state
Departure context
Arrival is operational data
A guest list tells you who booked. Check-in tells you who is actually ready to go.
As departure time gets closer, the useful question changes. The team no longer needs only the reservation count. It needs to know who has arrived, who is still expected and whether the live guest state matches the capacity the schedule is showing.
DockFlow keeps arrival status attached to the same guest and operation instead of turning check-in into a separate scanner log. That gives guides, front-desk staff and managers one clearer picture of readiness.
From booking to arrival
Book the guest. Give them a pass. Scan on arrival. Update the live operation.
Guest management becomes most useful when the record stays alive through the entire arrival workflow.
- 01Book
Create the guest record from the reservation rather than starting a separate arrival list later.
- 02Pass
Give the guest a mobile-ready pass with the QR code needed for the arrival workflow.
- 03Scan
Validate the guest pass with the DockFlow scanner at the entrance, dock or meeting point.
- 04Update
Move the guest into a checked-in state that remains attached to the operation.
- 05Run
Let the team compare expected guests with live arrivals as the experience gets ready to start.
Check-in stays connected
The scanner is only useful because of what it updates around it.
DockFlow treats QR scanning as part of the operating workflow. Booking creates the guest, scheduling gives the guest somewhere to be, and check-in changes the live readiness of that operation.
Online Booking
Keep the guest identity and reservation context from the moment the booking is created.
Explore booking ↗
02
Smart Calendar & Scheduling
See guest readiness alongside the departure and capacity the team is preparing to run.
Explore scheduling ↗
03
Team Operations
Give the people receiving guests a shared view of the operation they are supporting.
Explore team operations ↗
04
POS & Payments
Keep commercial context close to the guest record when the team is handling the arrival.
Explore payments ↗
05
Reporting & Insights
Turn connected guest and operational records into a clearer view of what actually happened.
Explore reporting ↗
06
Attractions & Admissions
Use the same guest-first arrival logic for ticketed venues and admission workflows.
Explore admissions ↗
The guest arrives prepared
Put the pass in the guest’s hand and the arrival state in the team’s view.
The guest-facing side should be simple: present the pass, scan, continue. Behind that interaction, DockFlow keeps the validation tied to the guest record and the experience they are joining.
- Mobile-ready guest pass with QR code.
- QR validation designed for real arrival points.
- Check-in state remains connected to the booking and departure context.
The moments that make check-in matter
Arrival gets difficult when the answer is split across a manifest, scanner and conversation.
The check-in workflow has to stay readable when the entrance is busy and departure time is getting close.
The group is almost ready. Two people have not arrived.
Live check-in state helps the team focus on the guests that still need attention instead of recounting everybody who is already there.
Several guests arrive at once with phones in hand.
The scanning interaction should stay short while the operational record updates behind it.
The person scanning is not the person making the departure call.
Check-in becomes more useful when arrival state is visible beyond the device doing the scan.
The team needs to understand the person, not only whether a code scanned.
Keeping the scan attached to the guest record preserves the context created earlier in the booking workflow.
One guest record
Keep the guest useful after the scan is over.
Check-in is one moment in a longer guest journey. DockFlow keeps the record connected so the same customer context can support booking, arrival, payment and the operational history around the experience.
Choosing QR check-in software
A fast scan is good. A fast scan that updates the operation is better.
When evaluating guest check-in software for tours, attractions or activities, look at what happens to the guest state after the QR code is validated.
Does the QR pass belong to the real guest record?
Validation is more useful when the scanner knows which customer and booking the code represents.
Does scanning update live arrival status?
The operating team should not have to reconcile a separate scanner log with the manifest.
Can the check-in state stay attached to the departure?
Arrival matters because the guest is expected somewhere specific at a specific time.
Is the workflow practical at a real entrance or meeting point?
Staff should be able to validate guests without turning the arrival into a complicated back-office interaction.
Can managers see the same readiness picture?
The value increases when the arrival state can inform the people deciding whether an operation is ready to move.
Does the guest record continue beyond check-in?
A connected platform keeps customer context available across the rest of the operating and reporting workflow.
DockFlow