// Mini POS wiki
Administrator Setup
Build one auditable register context from company Setup through Store, Terminal, profile, users, master data, tenders, posting, and output.
Purpose
Build one auditable register context from company Setup through Store, Terminal, profile, users, master data, tenders, posting, and output.
Role
Business Central administrator with BAA POS - Admin plus the required base BC permissions.
Prerequisites
Posting groups, tax/VAT setup, locations, customers/items, G/L and bank accounts, number-series policy, printer/network decisions, and payment-provider ownership.
Enable / Configure
Run Assisted Setup, then review POS Setup, Store overrides, Terminal overrides, Register Profiles, Fulfillment Methods, Tender Methods, Print Destinations, barcode/scale settings, tax, and EOD grouping. Register Profile precedence is exact: Terminal > Store > POS Setup > Compatibility when no profile is assigned. A missing or inactive assigned profile fails closed at its level and does not fall through to a lower assignment.
Steps
- Create and validate the Setup singleton and number series.
- Create Store with Location Code and cash customer; create Terminal and POS Users.
- Create a profile from Standard Checkout or Order and Fulfillment; validate it before assignment.
- Map POS Items/Customers to BC masters and test tax/posting groups.
- Configure tender settlement accounts and receipt/kitchen destinations.
- Open Effective Register Setup for the exact Store/Terminal and resolve every Required Setup row.
- Run First Sale before adding live EFT or hardware.
Expected Result
The effective page explains each visible, hidden, unavailable, or incomplete feature. One test sale can complete and post without changing configuration during the basket.
When Disabled
Disabled profile capabilities remove the UI and reject direct server calls. Missing prerequisites show Required Setup. Company policy and permissions remain stronger than profile choices.
Records / Accounting
Configuration lives in POS Setup, Store, Terminal, User, Register Profile, Fulfillment Method/Profile Fulfillment, Tender Method/Terminal Tender, Print Destination, barcode/scale, and master-data mapping tables. Setup itself posts nothing.
Recovery
Use Validate and Effective Register Setup. Deactivate configuration only after unassigning it; do not rename historical meaning. Historical outputs read sale stamps and enum fallback, not live descriptions.
Test IDs
LEARN-ADMIN-001 effective precedence; LEARN-ADMIN-002 posting readiness; LEARN-ADMIN-003 profile activation; LEARN-ADMIN-004 safe output setup.
Screenshots
Task 9 captures final setup evidence from one tagged package. Record company, profile code, Store/Terminal, Setup state, tagged demo-data version, tester/date, and Pass/Fail.