Moving a POS is not only a cabling and inventory task. Administrative Instruction (MF) No. 01/2026 requires notification to ATK when SEF use changes, including location, sale, transfer, deregistration or cessation of activity. The plan must protect continuity and correct fiscal identification.
Define exactly what is changing
Distinguish a physical move within one unit from a new unit, transfer to another owner, device replacement and deregistration. Each scenario may affect the unit number, POS, certificate, maintainer and solution registration.
Do not dismantle the old installation before the provider and responsible business owner confirm the procedure.
Controlled close of the old installation
Before change, review pending receipts, exports, reports, stock and correction history. Record the last transaction, stop time and authorizer. Retain data under business policy and applicable requirements.
If hardware will be reused, simply deleting the application is not deregistration.
Notification and new configuration
Follow ATK’s current notification procedure and work with the registered developer or maintainer. Verify unit, POS, solution code, fiscalization number and certificate before the first sale at the new location.
Where the maintainer changes, register that relationship under the relevant procedure.
Acceptance test after the change
Run a documented sale, print or electronic delivery, QR, correction and controlled connection-loss test. Then inspect reporting by location and operator.
- No old pending receipts.
- New identifiers confirmed.
- Correct certificate and device time.
- Printer and QR tested.
- Reports and stock assigned to the right unit.
- Handover signed by responsible people.
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
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