Learn Duited POS in a simple first-run flow.
This guide is prepared for new users, testers and early business users who want to understand the basic Duited POS workflow before using it in a real shop environment.
Start with these five steps
- Set up your business profile. Add the shop or business information used in records, receipts and reports.
- Add your first products. Create product names, selling prices, stock quantities and barcode or QR details when available.
- Record a test sale. Use checkout to create a simple sale and confirm that the receipt and sales record look correct.
- Check inventory changes. Review how the sale affects stock records and whether the product information is clear.
- Review reports and backup/export options. Confirm that the daily business records can be reviewed and shared when needed.
Core workflows to test
Checkout
Create a sale, check totals, confirm payment method records and review the generated receipt.
Products and inventory
Add products, update quantities, use barcode or QR details, and check stock movement clarity.
Purchase records
Review purchase documents, receiving, supplier invoice and payment status where available.
Reports
Check daily sales, stock-related information and export or sharing flows.
Device features
Test camera, barcode scanning, Bluetooth printer/scanner/cash drawer workflows if your setup uses them.
Backup and export
Confirm that important local business data can be backed up, exported or shared through user-controlled actions.
FAQ
Who is Duited POS for?
Duited POS is designed for small shops, retail counters, service businesses and trading businesses that need a practical Android-based POS and inventory tool.
Is Duited POS a full ERP?
No. The current public wording should position Duited POS as a practical POS, inventory and business record app for small businesses, not a full ERP system.
Does it require cloud sync?
Duited POS is described as local-first. Many important records are intended to be managed on the user's device, with backup/export actions controlled by the user.
How should testers report issues?
Please include the device model, Android version, screen or workflow being used, what happened, and whether the problem happened once or repeatedly.
Send feedback
Feedback is useful when it is specific. Tell us what you were trying to do, which screen you were using, what you expected to happen, and what actually happened.
Email: hello.duited@gmail.com