Skip to main content

Install certified POS in France

This article walks you throught the steps to launch a new or switch an old client based in France to a certified version of our POS and ensure it can operate legally in France.

1. Overview

In France, all sales made through a POS must comply with legal fiscal regulations. Each transaction must be correctly signed and transmitted to the fiscal authorities.

Smeetz provides a compliant and certified POS application, but compliance does not rely on the application alone. A correct setup requires close coordination between the client, Smeetz and the hardware provider to ensure that:

  • The organizer profile is correctly created and opened in EFSTA with accurate fiscal information

  • POS devices start seamlessly and are properly linked to the fiscal services

  • Sales are processed without errors

  • Fiscal receipts are generated and printed without inconsistencies

This article describes the overall POS setup and linking and the key elements that must be in place to ensure the system operates correctly and remains compliant over time.

Who does what at a glance

  • 🟦 Smeetz Implementation Manager completes section 2 (prerequisites) before the install date.

  • 🟧 Hardware provider performs sections 3 and 4 onsite.

  • Section 5 lists feature limitations to communicate to the client.

  • Section 6 is the joint validation checklist, signed off by the Implementation or Account management team.

2. Smeetz side prerequisites

🟦 Owner: Smeetz Implementation Manager. All items below must be completed before the hardware provider arrives onsite. The install will stall if any of them is skipped.

  • POS devices created in BO. Add each physical POS in Account Details → Peripherals → Devices and note the unique POS ID. See how to create devices.

  • Fiscal information filled in BO. Click on the account icon → Branding Details → General Info → Fiscal Information and complete every field (Company name, address, ZIP & City, SIRET / SIREN, VAT / Tax ID).

  • Tax ID saved on each POS. One Tax ID per account, same value for every device, but it must be saved once on each POS under Profile → Fiscale → Tax ID. Required so the device can communicate with EFR.

  • L2 ticket completed, backend setup done. Open a Jira L2 ticket so Smeetz tech can link each POS device to the organizer in the backend and create one POS configuration per device (configurations are not shared). The hardware provider cannot perform this step. Onsite install is blocked until L2 confirms completion.

  • Hardware provider added as user (to perform the test). Add the provider's contact email to the client's BO group so they can log in onsite, complete the install, and run the validation test.

  • Client appears on the EFSTA tracking sheet. Verify the organizer is listed on this sheet with a Badge ID assigned. If not, involve the Implementation or Account management team. Badge ID is generated only after Branding Details fiscal info is complete.

  • Onsite cashier confirmed. At least one cashier (or manager) with POS access must be present on install day to log in, open a sales session, and confirm the starting drawer amount.

  • Client briefed. The client must understand that sales cannot be processed during the install + testing phase.

→ See Final checklist for validation

3. EFR Installation (provider side)

🟧 Owner: Hardware provider. Performed onsite or during pre-shipment staging. All Smeetz side prerequisites in section 2 must be complete before starting.

  • Download the EFR France version from here specifically (we only got certified to use this version).

  • Run installer as Administrator and allow all firewall prompts.

  • The EFR service is auto-started. You can access it in your browser via:

    <http://localhost:5618/>

    If the page does not open: restart EFR Service or reboot the device.

  • Go to Profile tab and make sure "Offline" is not checked.

  • Copy the Badge ID from this sheet (provided by the Smeetz Implementation or Account management team) and paste it into the field Badge.

  • In the Attributes field add: Fis_Certification=B0634 and click Save.

➡️ EFR is now linked to the organizer in the EFSTA platform. After installing on POS, we need to verify POS ↔ EFR communication.

ℹ️ The fields in Données de base auto-populate only after the certified POS is installed (section 4) and the cashier has logged in for the first time. If you check this section before that, the fields will be empty (that's normal). Complete section 4 first, then come back here to verify.

  • Go to Données de base.

  • Check that the following is filled in (auto-populated from the BO fiscal info):

    • Company / Organizer name

    • Address

    • ZIP & City

    • SIRET / SIREN

    • VAT / Tax ID

❗ If any field is still missing after section 4 has been completed (POS installed, cashier logged in), the organizer profile is not set on EFSTA. Contact the Smeetz Implementation or Account management team. Do not proceed.

  • Make sure the following are filled in:

    • TL: the group ID (communicated by Smeetz)

    • TT: the device ID (communicated by Smeetz, one per POS, see Account Details → Peripherals → Devices)

    • SW = Smeetz POS

    • SWVERSION = 1.0.2

📸 At the end, take a screenshot of the Profil and Données de base pages and send to the Smeetz Implementation or Account management team so they can verify the fiscal info is correct.

4. POS installation & validation (provider side)

🟧 Owner: Hardware provider. Performed onsite, with the cashier present.

  • Confirm POS devices are created in BO and that L2 backend setup is complete (Smeetz prerequisite, see section 2).

  • If a previous POS version is installed: before uninstalling, open the POS settings and verify which device is currently selected. This prevents a popup error in the new FR POS. Then uninstall the previous version and delete the installer from the device.

  • Install the certified POS version for France (currently 1.0.2, we only got certified to use this version, do not substitute) on the POS devices.

  • Log into the POS with the cashier credentials (cashier or manager must be on site).

  • Select the correct POS for this device on first login (one configuration per device, set up by Smeetz L2 in advance).

If login is blocked → EFR config is incomplete, OR the device is not linked yet on the Smeetz side. Contact the Smeetz Implementation or Account management team / L2 if the connection still doesn't work.

  • Open the sales session and do a test sale.

  • Make sure the receipt is correctly printed.

📸 At the end, take a screenshot of the receipt.

5. France POS, Limited Features

France fiscal rules reduce available POS features. Make sure the client understands the following limitations:

❌ No multi-currency payments

Only EUR is allowed.

❌ No invoices generated in POS

Invoices are available in Back Office only.

❌ No invoices printed from POS

Only fiscal receipts from EFR.

6. Final checklist for validation

🟦 Smeetz side (must be ✅ before the hardware provider starts onsite):

  • Organizer created in BO.

  • Fiscal data filled in Branding Details → General Info → Fiscal Information.

  • Tax ID saved on each POS (Profile → Fiscale → Tax ID, same value for the whole account).

  • POS devices created in BO.

  • L2 ticket complete: devices linked + one config per device created.

  • Hardware provider user added to the client's BO group (so they can perform the test).

  • Organizer appears in EFSTA (Badge ID available).

🟧 Provider side (onsite):

  • EFR installed.

  • EFR opened on http://localhost:5618/

  • Offline not checked.

  • Badge ID filled.

  • Attribute Fis_Certification=B0634 set in Profile.

  • Données de base filled:

    • TL = group id

    • TT = device id (one per POS)

    • SW = Smeetz POS

    • SWVERSION = 1.0.2

  • Certified POS installed.

  • POS login successful.

  • Test sale processed and receipt printed correctly.

  • Screenshots (Profil, Données de base, receipt) sent to the Implementation or Account management team.

✅ Implementation / Account management sign-off:

  • Fiscal fields and receipt validated by the Smeetz Implementation or Account management team.

Did this answer your question?