Welcome to our newly launched guide!
New to Auphan? Start hereLearn the basics in order›
Managerial ProceduresEmployees, hours, transactions & reports›
Clover SetupSetting up your Clover hardware›
Knowledge BaseEssential back end tasks and how-tos›
Operational›
TroubleshootingFix common issues›
Clover
›
Add and remove employees
Adding Employees
Removing Employees
Change employee hours
Recalling Previously Closed Bills
Can't find an invoice? It may be archived
Employee labour report
Support de-Tech-tives
24/7/365 — always here for you 😊
We want to be your partner in crime-fighting against issues and problems.
So if you can provide the best information — including photos/screenshots/videos — that gives our de-tech-tives the best context and evidence to help you much faster.
Customizable Buttons Reference Guide
Every customizable button on the ordering screen, and what it does. Tap a button for its purpose and when to use it — or search to jump straight to one.
Integration Partners
Every partner Auphan integrates with, grouped by what they do. Tap a partner for details — or search to jump straight to one.
Quebec Web-SRM
Web-SRM is Revenu Québec's fiscal system.
Every restaurant operating in Quebec must be connected to it.
A Web-SRM QR code must be printed with every invoice.
Click here to learn more — Revenu Québec's official page on mandatory billing in the restaurant sector (opens in a new tab, so this guide stays open).
What it is & why it matters
Scanning the QR code on a Quebec receipt opens Revenu Québec's record of that exact transaction — it's how the province tracks sales for tax and audit.
- Native integration. Auphan talks directly to Revenu Québec's Web-SRM — no third-party connector. Every invoice is registered and its QR code generated automatically.
- Compliant invoices, automatically. The QR code, the tax lines (TPS/TVQ) and the audit trail are handled for you. Staff don't do anything differently at the till.
- Hardware MEV still works. If you're on a legacy MEV unit, Auphan keeps working with it in parallel until you choose to move to Web-SRM.
For your staff
What's different day-to-day›
Once it's running, the changes your staff actually notice are small:
- Every receipt prints in French, with the QR code, the TPS/TVQ tax lines and “FACTURE ORIGINALE.”
- Offline mode. If the internet drops, the POS keeps printing invoices — they're flagged as offline and you'll see a Web-SRM offline notification. When the connection returns, the queued invoices upload to Revenu Québec automatically; no action needed.
⚠ What you can't change on a Quebec invoice›
This is the big one for front-line staff. Because Web-SRM sends fiscal documentation to Revenu Québec the moment an invoice closes, a closed Quebec invoice can't be freely edited the way it can elsewhere.
Reopening a closed invoice (“recalled” invoices)
When you use Recall Invoice on a closed invoice, Web-SRM reverses the original transaction with Revenu Québec and locks the invoice down. From that point you can only change the payment type.
What you can do: remove, add or change payments, reclose the invoice, and reprint merchant or customer receipt copies.
Recall = payment fixes only. For an item mistake on a closed invoice, don't recall — create a refund instead. Train staff on that difference, and verify items are correct before closing an invoice.
Common cases:
- Paid cash, wants to pay by card: Recall → remove the cash payment → add the card payment → reclose.
- Wrong item or quantity on a closed invoice: reclose the recalled invoice as-is, then create a refund invoice for the correction.
- Need to remove a closed invoice entirely: you can't delete a recalled one — reclose it with the original payment, then create a separate refund invoice to reverse it. That keeps the audit trail Revenu Québec requires.
Which function to use
- Cancel Invoice — for open invoices that haven't been closed yet.
- Refund — for item corrections after an invoice is closed.
- Void Payment — to remove a payment before reclosing the invoice.
- Failed to Pay — when a payment cannot be processed.
Delivery & takeout orders can't be modified›
The problem: staff can't add or remove items on a delivery or takeout order, and are told to cancel and create a new bill.
Why: the order was closed automatically after payment. Web-SRM immediately sends the fiscal documentation to Revenu Québec, which prevents any item changes from that moment on.
What to do:
- Turn off auto-close in Management > Online Orders > “Close Paid Orders.” Staff then close orders manually after verifying the items, which leaves a window for modifications.
- For orders that are already closed: items can't be modified (Quebec regulation). Create a new order with the correct items, and issue a refund for the original if needed.
Deleting an invoice that hasn't been paid yet›
When you delete an open invoice (items entered, not yet closed), Web-SRM gives you two choices — pick the one that matches what actually happened, because each sends a different record to Revenu Québec:
- Cancel Invoice — the order won't be paid for a normal reason: the customer changed their mind before paying, it was entered wrong, a table walked out before ordering, or it's a duplicate. Sends a cancellation record, and items return to inventory where applicable.
- Failed to Pay (Annulation) — the order should have been paid but wasn't: the card was declined, the customer couldn't pay, a dine-and-dash, or a terminal failure. Sends a “failure to pay” record, which is a different type of fiscal record for unpaid transactions.
Either way the invoice is closed out and can't be reopened, and both are logged for the audit trail.
Closed invoices can't be deleted directly — you must recall first, after which only payment changes are allowed (see above).
Teach staff the distinction: Cancel = a customer or business decision before payment. Failed to Pay = a payment attempt that was unsuccessful. The choice affects financial reporting and tax implications, so it isn't cosmetic.
Delete reasons & the audit trail›
Both Cancel Invoice and Failed to Pay require you to pick a delete reason from your configured list. Common reasons include customer cancellation, staff error, payment declined, customer unable to pay, system error, and duplicate order.
Choose accurately — the reason is sent to Revenu Québec, is required for compliance, helps with loss-prevention analysis, and is useful for spotting training needs.
If partial payments exist you may need to void payments first; the system will guide you through the steps, and each payment removal is tracked for audit purposes.
Where deletions are recorded
- Web SRM Invoice Log — all delete actions with their reasons.
- Web SRM Txn Log — the technical transactions sent to Revenu Québec.
- Invoice Logs report — the complete deletion history, with employee details and timestamps.
Web-SRM reports›
Turning on Web-SRM adds three reports:
- Web SRM User Report (Receipt) — the summary of recorded totals mandated by Web-SRM.
- Web SRM Invoice Log — every action on invoices (deletes, prints, etc.).
- Web SRM Txn Log — all data sent to and received from Revenu Québec; also handy for troubleshooting a specific invoice.
Receipt footer placement — tips above the QR code›
You can control where your receipt footer prints relative to the mandatory Web-SRM elements — useful for putting tip suggestions right above the QR code, where customers scan. In Management > Store Setup > Receipt Setup, add the marker [web_srm_footer] in your footer, for example:
Thank you for your visit! [web_srm_footer] Suggested Tips: 15% = [SUBTOTAL=15] 18% = [SUBTOTAL=18] 20% = [SUBTOTAL=20]
That prints in this order: your thank-you message, the Web-SRM tax and payment information, your tip suggestions, then the Web-SRM QR code and transaction details.
Without the marker, your footer prints between the Web-SRM payment info and the QR code (the default behaviour).
Other uses
- Promotional messages — marketing content placed strategically on receipts.
- Contact information — store details or social media handles.
- Special instructions — pickup times, loyalty program info, and so on.
All mandatory Web-SRM elements always appear. The marker itself is removed from the printed receipt, and extra line breaks around it are cleaned up automatically.
One-time installation and back-office configuration. Restaurant staff don't need anything in this section — your Auphan onboarding contact handles it.
Before you start — dependency install›
Collect the four Revenu Québec numbers from the customer:
- User Identification Number
- User Authorization Code
- QST number — Taxe de vente du Québec
- GST number — Taxe sur les produits et services
Revenu Québec issues these when the establishment registers for SRM/Web-SRM, so the customer's accountant usually has them on file.
Then install the Web-SRM dependency: download Auphan's Web-SRM install script from the Auphan updates page and unzip it into the POS install folder (e.g. c:\auphansystem or d:\restaurant). Open the unzipped folder and run install-as-admin.bat as Administrator.
POS setup in Management›
Taxes
Create the mandatory GST/TPS (5%) and QST/TVQ (9.975%).
For any service charge or other charge, set its Priority the same as TPS and TVQ, and set Ontop Tax to TPS and TVQ.
System config
In System Configuration, set SRM System = SRM - Quebec WEB. Then log out and back into Management — the Web SRM setup page appears under Online Services.
Web SRM setup page
Fill in the establishment details, assign the QST and GST taxes, and set the time zone to match the establishment.
Press Save and Generate Initial Certificates to register each station with Revenu Québec. Come back and press it again any time stations are added later.
Certificates & maintenance›
Certificates are generated per station and stored in the server's Windows certificate manager. That means if the server changes, you must regenerate the certificate for every station.
Use the Certificate section at the bottom of the Web SRM page to renew, delete or verify certificates. Select a station from the dropdown to see its certificate information.
On recent versions, use this section to verify a certificate exists and is valid. If it isn't, delete the certificate in question so a new one can be generated — you'll need to give it a different name, e.g. “Clover 3 certificate 2”. After generating, use Check Certificate to confirm.
Certificate errors
- “Valeur invalide dans la demande de signature de certificat (CSR)… codRetour: 16” with a
CSR/CN=value — the Identification Number entered is not correct. - Same error with
CSR/surName=— the station name contains characters Web-SRM rejects. Remove special characters such as( )from the station name, or generate the certificate manually with a name that doesn't contain them. - “Failed to create COM object 'SrmCertificateManager.CertificateManager': Invalid syntax” — the dependency installation didn't complete. Re-run install-as-admin.bat as Administrator.
QR code size›
Under Management > Web SRM you can set the QR code size as a percentage width. There are two settings:
- Large — for mobile printers like the Clover Flex and PAX.
- Small — for regular full-size thermal printers.
Debug logging›
A Debug Log checkbox in Management > Web SRM enables detailed logging for troubleshooting. It turns on the web_srm_debug flag in the system configuration, which produces more detailed logging for Web-SRM transactions and operations.
It's useful for:
- Troubleshooting connection issues with Quebec's Web-SRM service
- Debugging certificate-related problems
- Investigating transaction submission failures
- Providing detailed logs to support for issue resolution
Troubleshooting›
Error: “You cannot close invoices without SRM device on this station.”
Don't forget that Web-SRM requires the invoice printer to be configured for the station.
Legacy hardware MEV›
If the site is still on the older hardware SRM/MEV box, it keeps working alongside — there's no need to switch immediately. Setup is an installer / serial-hardware job rather than a front-line task:
- In System Config the SRM System is set to SRM - Quebec.
- The two taxes must be named exactly “TPS” (5%) and “TVQ” (9.975%), or the MEV won't recognize them.
- The SRM connects by serial cable to the server, or via Auphan's Comm2IP utility for client stations.
- The SRM printer is added as a Native Printer (SRM - Epson driver, CP1252 encoding).
- Invoices must print in French.
Baud-rate, cabling and RealTerm diagnostics are covered in Auphan's installer docs.
Customer Tipping Screens — Auphan vs Clover
Clover eCommerce
The Basics›
Auphan’s online ordering system OftenDining is integrated with Clover eCommerce for taking online payments.
OftenDining services that can utilize Clover eCommerce are as follows:
- Online Ordering
- Table QR Payments
- e-Gift Cards
Apple Pay & Google Pay are also supported by Clover eCommerce services.
To sign up, please talk to your Clover rep if you already have a Clover account.
If you currently don’t have a Clover account, your Auphan contact will be happy to refer you to quality Clover contacts.
1. Get your credentials from Clover›
2. Enter them into Auphan›
Go to Store Settings → Payment Processing and set:
- Active Payment Processor — Clover
- Clover Merchant ID
- Clover Public Token
- Clover Private Token
Optional features & toggles›
The card form always asks for card number, expiry, CVV and postal/zip. Everything below is additive — it only appears when you switch it on.
- Clover Enable Google Pay — shows the Google Pay button. Google Pay must also be enabled on your Clover account.
- Clover Enable Apple Pay — shows the Apple Pay button. Only appears for guests on Safari with Apple Pay set up, and your domain must be verified first (below).
- Clover Show Cardholder Name — adds a cardholder-name field. An optional fraud signal; nothing else depends on it.
- Clover Show Street Address — adds a street-address field.
- Clover Enable 3D Secure — sends card charges through 3D Secure 2.0.
Turning on Apple Pay & 3D Secure in Clover›
Ticking the boxes in Auphan isn’t enough on its own — these two also have to be switched on inside your own Clover dashboard.
Apple Pay — verify your domain
- In the Clover Merchant Dashboard, go to Settings → Apple Pay → IFrame integration.
- Click Enable Apple Pay, enter your Often Dining domain (usually oftendining.com), and click Verify.
- The status needs to read Verified.
You can ignore the API Integration section on that page — it’s only for merchants migrating an existing Apple Merchant ID from another processor.
3D Secure
- Go to Settings → Fraud Tools → 3D Secure.
- Enable 3D Secure 2.0 and pick a provider — CardinalCommerce or Ravelin, either is fine.
- Ask Clover support to enable 3DS entitlements on your account. Only Clover staff can flip this, and without it the toggles do nothing no matter what you set.
Troubleshooting
Payment declined — postal code mismatch›
Clover checks the billing address at the card-network level (AVS). If your Clover account enforces AVS strictly, any order where the guest’s billing postal/zip doesn’t match their bank’s records is declined — before it ever reaches us.
Fix: loosen the AVS rules in your Clover dashboard.
Currency mismatch error›
The error reads: “Currency provided in request does not match default currency code for the merchant.”
Your Clover account has one fixed currency. Your store’s country setting in Often Dining decides what we send (US → USD, Canada → CAD).
Fix: make the store’s country match the currency on the Clover account.
Saved cards not working›
Saved cards need multipay tokens enabled on your Clover account.
Fix: contact Clover support and ask them to enable multipay tokens.
Apple Pay button not appearing›
The button only ever renders for a guest using Safari, on an Apple Pay-capable device, with at least one card in their Wallet. It will never show on Chrome, Firefox, Android, or a Safari session with no card set up — that’s normal, not a fault.
If it’s missing even on Safari with a card in Wallet, check your domain still shows as Verified under Settings → Apple Pay → IFrame integration in your Clover dashboard.
3D Secure not firing›
If Clover Enable 3D Secure is ticked but charges sail through without a challenge, check these in order:
- 3DS is enabled in your Clover dashboard — Settings → Fraud Tools → 3D Secure, with a provider selected.
- Clover has enabled 3DS entitlements on your account. Only Clover support can do this, and without it the dashboard settings have no effect.
- The card is 3DS-enrolled. Most real consumer cards are — but test card numbers generally are not, and won’t trigger 3DS.
Initial Setup
1. Initialize your Flex'sClover's out-of-box setup — skip LTE mode
›
If you have just received your new Flex's, you must initialize each and every Flex terminal before we can continue.
2. Download the Auphan appSpecial link + your Clover dashboard login›
To get the Auphan app onto all of your Clover Flex's, you must use the following link. You must know your username and password to your Clover dashboard login — otherwise you cannot download the app.
www.auphansoftware.com/clover_install.php
3. Clover Settings
The following tasks may require the super admin login that was initially provided to the owner of the Clover account.
Log in to your Clover dashboard here (opens in a new tab, so this guide stays open):
www.clover.com/login
Enable "Quick Access"›
It is very important to have Quick Access enabled so that employees can use the minimum amount of features to perform their duties, which includes access to the Auphan app.
Set up tip options›
Set up offline mode to continue taking card payments (no debit, only credit cards)›
Clover devices allow you to process offline card transactions by storing them locally and submitting them for authorization once internet connectivity is restored. Your staff won't even notice when there is a temporary internet outage, as the flow is exactly the same as if the internet is still working.
Please note that this only applies to credit cards, as debit card transactions require a live internet connection to perform.
Turning off Clover's final receipt dialog — highly recommended›
If the receipt dialog is not acknowledged by either the customer or the server, this can prevent Clover from completing the transaction, and therefore preventing the table from auto closing on the POS. Turning it off is optional but highly recommended.
Most customers don't require the final copy of the invoice unless it's for a business write-off. If this receipt dialog is turned off, you can always print the invoice manually for the client.
Extremely important: turn off "dip a card to activate the Sale app" (done on the Flex itself)›
4. Auphan App Setup
The Auphan HD app on the Clover Flex operates in three modes:
Station Mode on the Flex
Print sticker labels for each of your Flex's.
Important Features To Know
Exiting Lockdown Mode — 3 Ways›
-
Normal Exit
Only staff that belongs to a user group with the privilege to exit the app can exit.
-
Emergency Exit
Hold the top left corner for 5 seconds, then enter a user login code with sufficient privileges.
-
Alternate Emergency Exit
The debug menu also lets you make changes, such as adding a replication server IP later.
Slide to confirm›
Enable slide-to-confirm for payment types to prevent applying accidental payment types such as cash.
Optimize the top and bottom buttons›
Due to the compact screen size of the Flex compared to a full sized station, you can customize what buttons to make available for the top row and bottom row.
Flex printer settings — includes Flex Pocket setup›
Clover Pocket printer setup for dynamically choosing the nearest printer›
Set the printer for Clover Pocket stations to "Ask on Print".
New — Non Table Map Mode›
If you prefer to enter the table number directly, we have a station mode that doesn't use table maps — but rather, uses an alphanumeric keypad to open a table directly.
Pay at Table Mode
First Steps
Before continuing with Pay at Table setup, please open your freshly downloaded Auphan app on the Flex and follow the next three steps:
- Highly recommended — print sticker labels for each of your Flex's.
- Connect your Auphan app to the server.
- Set up the Flex Stations in Management.
See Pay at Table in action
Take a minute to watch how a payment flows at the table — the server brings the Flex over, the guest pays and tips on the spot, and the table closes itself. The settings below fine-tune exactly this experience.
User group settings›
User group settings determine whether staff see their own invoices or see all invoices (for managers).
5. Auphan app setup under Payment Processor settings
This is where the Auphan app is connected to your payment processor inside Auphan POS management.
Please be aware this is also where you can change from using Clover's native tip screen displayed to customers, or use Auphan's own in-house tip screen. To learn more about the differences, see Customer Tipping Screens — Auphan vs Clover.
General Operations
General
Welcome! — User Interface Overview
A quick tour of the main screens you'll use day to day. Tap a screen below to explore what each area does.
Login Screen
Table Maps — Full Table Service
Ordering Screen
Three Dots = More Options
Light Mode Option
Clover Flex Interface Overview
Station Mode on the Flex runs exactly the same as a full screen station. Because the screen is smaller, though, a few parts of the interface work differently — here's what to look for.
Interactive Gallery of User Operations
Table Map Overview
Menu Ordering Overview
Invoice Overview
Light Mode Option
Clock In / Clock Out
Opening a Table
Assigning Seats
Renaming Seats
Coursing - Fire & Hold
Menu with auto coursing setup
Open coursing, starting from “Course 1”
Purely optional coursing
Create a Delivery Order
Create a Takeout Order
Close Transactions
Split a Bill
Basic Splitting — Splitting From One Seat
Basic Splitting — Seat Grouping
Group multiple seats onto shared invoices — e.g. S1 + S3 = one invoice, S2 + S4 + S5 = one invoice, and so on.
Basic Splitting — Seat Selection Was Used
The following video assumes you have assigned specific seats to the items ordered.
Various Seating/Splitting Views
Split By Seat
Split By Seat instantly splits all the seats as is — every seat number becomes its own invoice. If you've properly assigned each seat to its ordered items and everyone wants to pay for themselves, this is the easiest method. You can also access “Split by Seat” under the More section and simply split, but without printing.
Split X Ways
Split an Item
Commonly used splitting method that's usually done at the very end.
Splitting an item early
Splitting an item early in the dining experience, when a guest tells you up front.
Split by Accident — Re-combining Split Invoices
Reopening a Closed Transaction
Find Missing Open Invoices
Apply an Item Discount
Apply a Bill Discount
Splitting a Big Table Group
We have various ways to help you split a big group easily. The examples below are all based on a table of 20 people.
Combine and Print
Example: Seat 1, Seat 4, and Seat 5 are going to pay together — you combine those three and print.
Moving a Table
Changing the Number of Guests
Cash Out Report
Charged the Wrong Table — Transfer Payment
Pay at Table (PAT) Mode
In this classic payment mode, taking the payment through Auphan's PAT mode will automatically close the table.
- Set up user groups to restrict servers to only seeing their own invoices, as opposed to managers seeing the entire restaurant's open invoices.
- Split invoices will show up accordingly in PAT mode.
Customer Tipping Screens — Auphan vs Clover
The following are screenshots comparing the Auphan tip screen vs. the Clover tip screen.
Here are some comparison of features differently unique to both Auphan and Clover:
- Auphan tip screen calculates tip based on the total net amount (or gross amount with tax) when there is a split payment. For example, if a customer pays with gift card or cash and then pays with credit card, the suggested tip can be based on the entire net/gross amount.
- Auphan tip screen defaults to dark mode, as opposed to Clover's tip screen defaulting to white mode, which can light up the customer's face in a darker restaurant.
- Clover tipping options can add playful labeling and smart tipping that can suggest a flat tip amount under X amount of dollars of purchase.
- Both tipping screens can suggest tip before tax or on top of tax.
You can switch between Clover's native tip screen and Auphan's in-house tip screen under Payment Processor settings.
Gift Card Scanning Functions
With the built-in camera of the Clover Flex, you can now sell or redeem a gift card right at the table side with your guests.
Activating a gift card
Here is a quick video of what the process is like to activate a gift card:
Redeeming a gift card
Here is a video of redeeming a gift card via the Flex:
Redeeming a gift card in PAT mode
Voids & Refunds
Voids
Voids can only be done on the same day, before batch closes. Voiding means that there will be no action taken at all on the customer's credit card.
Reasons why it's recommended to use voids instead of refunds, especially on the same day:
- Changing payment type — the customer paid with Visa, but wants to pay with AMEX now instead.
- The invoice total has changed, so you simply want to start over again. Void, make the adjustment to the invoice, and then do a fresh new charge to the guest's card payment.
Refunds — Clover Flex Integration
For refunds, think of it as creating a brand new invoice to negate either one item from a past existing invoice, or all the items of a previously generated invoice.
Full Refund
Coming soon.
Partial Refund
Coming soon.
Manual Refund on Clover — Last Resort
Coming soon.
Troubleshooting
Choose the issue that matches what you're seeing:
Good to know — nightly Flex reboot
Poor WiFi & networking — the root cause of many issues
Your Flex terminals talk to both the Auphan server and Clover's payment network over your WiFi. When that connection is weak or unstable, the symptoms show up everywhere else — and they're easy to misdiagnose as app problems.
Symptoms that usually trace back to networking
- Tables not closing automatically after a successful payment (lost transmission)
- The Auphan app showing a disconnected screen
- The Clover payment screen not appearing after initiating a card payment
- Slow or unresponsive behaviour that comes and goes with location in the restaurant
What a solid setup looks like
- A dedicated, secured network for your POS — never share the guest WiFi with your terminals.
- Strong coverage everywhere staff take payments — patios, private rooms and far corners included. Dead zones are where lost transmissions happen.
- Business-grade router and access points — consumer equipment struggles with a busy restaurant full of phones.
- A reliable internet connection — payment confirmations depend on it in real time.
If you are unsure about your network, please talk to us before going live — a one-hour network review is much cheaper than a dinner rush of failed payments.
Card payment successful, table/invoice did not auto close
It can be confusing and frustrating when tables don't auto close when they should after a successful guest payment.
We now have a built-in auto recovery and manual recovery with Clover payments.
- Auphan will automatically try to recover the payment to auto close the table — for up to four minutes.
- If this still fails, or you don't want to wait, you can simply hit "Verify Clover" to close the table.
Final Fallback — Close Table Manually
This requires a manual close button to be set up first, and it may be called "Standalone Visa", "Standalone MC", "Offline AMEX", etc.
Setting up Verify Clover
Why does this happen?
Unfortunately, there are many variables that are out of the POS software's control that could lead to this result, such as:
- Weak or intermittent local network / WiFi (wireless is never 100%, and the signal is only sent back once from Clover — or any payment processor in general).
- Intermittent internet packet loss (signals can intermittently get lost over the internet) and may not even reach the restaurant.
- Highly unlikely, but still possible — Clover's servers didn't quite send the return confirmation transmission.
To be clear, these factors affect how all payment processors relay with an integrated POS.
Quick Access button disappeared
Unfortunately, this is a Clover issue — it's a bug where the Quick Access button will randomly disappear and then reappear (if at all).
We have informed Clover of this issue, but have never heard back if they have found the bug and fixed this disappearing button issue.
Auphan app showing a disconnected screen
There are a couple of reasons that can cause this to happen:
- The Flex may be connected to a different WiFi network. This may not be obvious at first. This can happen when the Flex was first being set up: if it connected to more than one WiFi network, the Flex will default to the other network it has connected to before if the primary WiFi connection cannot be found.
- Are ALL of your other terminals also showing a disconnect screen? If so, there are two things to check — but the first thing is to see if the server computer is still on. If the server is still on for sure, then you need to check if your local area network went down. If you still need help, please reach out to tech support.
- The IP address of the server computer changed. Some installers label the server computer with the IP address, and it would look something like
192.168.0.99. If you know for sure the server IP address has changed, please click on the cog wheel on the bottom right to enter the new IP address.
How to identify your Auphan app version on the Flex
Sometimes when troubleshooting, or when Auphan releases a new version and you aren’t sure if you have received the new version, it is very helpful to be able to check what version you are on.
How do I update my Auphan version?
Auphan app updates are managed by Auphan — they aren’t something you download on demand from the Clover App Store. To move up to a newer version:
- Your account must be on an active Auphan support plan.
- Contact Auphan to arrange the update — see Tech Support for how to reach us.