ATK’s register separates SEF solutions by certified platform, so device choice is not only about screen size. Before installation, match the proposed device, platform and version against the live register; a tablet or phone should not be treated as a fiscal point unless the solution’s current official status clearly covers it.
Desktop or laptop
Best for a fixed counter, large catalogues, barcode scanners and thermal printers. A larger screen supports cart review and reporting.
Tablet
A tablet can be useful for orders, reports or management. Before treating it as a fiscal point, confirm that the exact platform and version appear as certified in ATK’s register.
Phone
A phone can help with monitoring and mobile management. Do not present it as an easyPos fiscal device without an official entry covering the relevant platform and version.
- Match the version to ATK’s register.
- Test printing before live use.
- Use individual operator accounts.
- Separate the fiscal POS from management access.
The June rule: at least one suitable environment
The 22 June 2026 amendment replaced wording that could be read as multi-device support. The current text requires SEF installation and use on at least one suitable device or environment, such as PC, laptop, tablet, smartphone or another suitable device.
This does not mean every certified SEF runs on every listed platform. Check the actual platform in ATK’s live product entry.
Check certification scope before installation
ATK’s public register is the official source for verifying easyPos status. Check the active entry directly because its version and covered platforms can change.
Before installation, match the registered version and platform type to the device. A responsive management view does not automatically mean every device is a certified fiscal point.
A procedure that protects continuity
System behavior and staff procedure should be designed together. Define who checks the device, connection and transaction queue at the start and end of a shift. During an incident, staff need a clear status and must avoid actions that create duplicates.
A short incident record—time, device, operator and action—makes the post-recovery check easier.
Test before the procedure is needed
Do not wait for a real outage to discover system behavior. Test controlled scenarios and repeat them after material device, network or configuration changes.
- Work with and without internet.
- Restart with pending transactions.
- Synchronization and duplicate control.
- Handover to the next operator.
Pre-launch check
Use this guide as a basis for discussion with your team and software provider. The actual setup depends on your activity, locations and internal procedures.
- Define items, tax rates, prices and payment methods.
- Set operator roles and shift responsibilities.
- Test sales, corrections, offline work and reports.
- Document the workflow and train staff before activation.
Practical questions
Can every phone or tablet be a fiscal point? +
Not merely because the management interface is responsive. Check the platforms covered by the active SEF entry in ATK’s register before installation.
Must SEF support every device type? +
No. The amended wording requires installation and use on at least one suitable device or environment.
Who should review status after an interruption? +
The shift supervisor or designated owner should verify the queue, responses and any transaction requiring intervention.
How often should the workflow be tested? +
Test before launch and after significant changes. A short periodic test also keeps the procedure familiar to staff.
Must ATK be notified when a SEF location changes? +
Yes. The instruction lists location, sale, transfer, deregistration and cessation of activity among changes to be notified under ATK procedures.
Want to see easyPos in your business?
Tell us your type of activity and sales locations. We will show you a tailored workflow.
Request a demonstration