Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v19.0
License
Aura
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1666 lines (Python / XML / JS)
Overview & Description
Aura Odoo TechSupports:Odoo 20 Community POS SMS OTP Verification20.0.1.0.0: for Odoo 20 Point of SaleCharge a customer's account only with a code they actually received.When a cashier takes a payment that goes on a customer's account, the till texts a six-digit code to the customer's phone and waits for it. No code, no payment. Every attempt is written to a log you can read in the back office.✓Opens by itself when the flagged payment method is tapped✓Code expiry, resend cooldown and wrong-code limit set per shop✓Odoo SMS, Twilio or MSG91, plus a test provider for setupDepends on Point of Sale and SMSPer shop switchPer payment method 6digits in every code, random on each send5 mindefault life of a code, you can shorten it3wrong tries by default before the code is locked4ways to send: test, Odoo SMS, Twilio, MSG91 what you getA second factor for the till1A code before creditTap the flagged payment method and the dialog opens and sends the SMS on its own. The cashier sees the customer name and the number as ***4562, never the full number or the code.2Only where you want itTick Check by SMS OTP on a payment method (normally Customer Account) and switch the feature on per shop. Cash, card and every other method behave exactly as before.3Checks the customer firstNo customer on the order, or a customer with no phone number? The till says so and sends nothing. The message names the customer so the cashier knows which record to fix.4Timers the cashier can readA countdown ring shows the time left and turns amber in the last 30 seconds and red when the code has expired. Resend is greyed out and counts down its cooldown.5Brute force stops at the limitAfter the allowed wrong tries the code is locked. Resend issues a fresh code and resets the counter, and a new code retires the previous pending one for the same order.6Asked once per orderAfter a good code, further payments on the same order do not ask again. If the cashier changes the customer, the verification is cleared and the next payment asks again.7Four ways to sendA test provider that only writes to the server log, Odoo SMS, Twilio and MSG91. With Odoo SMS, a refusal from the gateway (for example no credit) is reported to the cashier instead of being silently accepted.8A log of every codeCustomer, number, session, shop, provider, whether the SMS went out, attempts used and the final status: verified, pending, expired or failed. List, filters and a form per record under Reporting.9Secrets stay off the tillThe stored code can only be read by Settings administrators and is compared in constant time. Twilio and MSG91 keys are limited to Point of Sale managers. Only Point of Sale users can call the send and verify routes. see it in actionAt the tillReal captures from Odoo 20: a running Point of Sale on a scratch database with Odoo demo data, using the built-in test provider. For these captures the code was read from the database, because the test provider sends no real SMS.The cashier picks the customerCustomer Account is on the payment screen as usual. Choosing it is what starts the verification.Code sentThe dialog sends the SMS as it opens. The ring counts down the code's life and Resend counts down its cooldown.A wrong codeEach wrong try costs one attempt and the dialog says how many are left.The right codeA short confirmation, then the dialog closes and the payment line is added.Too many wrong triesThree wrong codes (the default) lock the code. Only a fresh code from Resend lets the cashier continue.The code runs outShown here with a 30 second expiry so the capture did not take five minutes. Verify is off until a new code is sent.ResendA new code starts a new countdown. The ring is amber because this capture used a 30 second expiry.Payment goes throughAfter the code is accepted a toast confirms it and the Customer Account line is on the order, ready to Validate.No customer yetThe cashier is asked to pick a customer first. Nothing is sent.No phone numberThe customer record needs a phone number. The alert names the customer. set it upIn the back officeTwo switches: the payment method, and the shop. The same options are on the shop form and on the Point of Sale settings page.Flag the payment methodPoint of Sale, Configuration, Payment Methods. Open Customer Account and tick Check by SMS OTP.Switch it on for a shopOn the shop form: the master switch, the SMS provider, code expiry, resend cooldown and the wrong-try limit.Provider credentialsPicking Twilio or MSG91 shows their credential fields, here on Point of Sale settings under Payment. Odoo SMS and the test provider need none.Every code is loggedGreen is verified, red is expired or failed, and the attempts column shows how many tries each code took. The list opens on today's records.A verified recordCustomer, number, session, shop, provider, the attempts used and the time of verification.A failed recordA code locked after too many wrong tries keeps the attempt count and the reason.Where to find itPoint of Sale, Reporting, OTP Verification Logs. Managers see every record; a cashier sees only the codes of their own sessions. how it worksFour steps1InstallApps, search for POS SMS OTP Verification, Install. It depends on Point of Sale and SMS, which Odoo installs for you.2Flag the methodPoint of Sale, Configuration, Payment Methods. Open Customer Account (or any method) and tick Check by SMS OTP.3Switch it on for a shopOpen the shop, turn on Customer Account OTP Verification, choose the SMS provider and set the timings.4SellAt the till, pick the customer, choose the method and enter the code the customer reads out or shows. That is all.Good to know. The test provider sends nothing: it writes the message, code included, to the Odoo server log. Use it to try the flow, then switch to Odoo SMS, Twilio or MSG91 before real customers. The customer's number is read from the Phone field of the contact. The code is sent and checked by the server, so the till needs its connection to Odoo while the dialog is open. referenceEvery settingCheck by SMS OTPOn the payment method. Only methods with this ticked ask for a code.Customer Account OTP VerificationMaster switch, per shop. Off means no code is ever asked for.SMS ProviderTest provider (server log only), Odoo SMS (IAP), Twilio or MSG91.OTP Expiry (sec)How long a code is valid. Default 300, minimum 30.Resend Cooldown (sec)How long the cashier waits before asking for another code. Default 30, minimum 10.Max Wrong AttemptsWrong codes allowed before the code is locked. Default 3, minimum 1.TwilioAccount SID, Auth Token and From Number in E.164 form such as +14155552671. SID and token are visible to Point of Sale managers only.MSG91Auth Key (managers only), an optional Template ID and a Sender ID (default POSVER). With a template the flow API is used, without one a plain SMS is sent.OTP Verification LogsPoint of Sale, Reporting. Filter by pending, verified, failed or expired; group by customer, session, status or provider. questionsBefore you askCan the cashier see the code?No. It travels by SMS to the customer. The till is never sent the code, and on the server only Settings administrators can read the stored value.What if the SMS does not go out?The dialog shows a warning with the reason from the provider. The cashier can use Resend once the cooldown is over, or cancel, and no payment line is added.What happens if the customer changes mid-order?The verification is cleared. The next payment with a flagged method asks for a new code for the new customer.Does it work with payment methods other than Customer Account?Yes. The tick box is on every payment method. Customer Account is the usual choice because it is the one that charges a customer without money changing hands.Do I need Twilio or MSG91?No. Odoo SMS works with Odoo's own credits. Twilio and MSG91 are there if you already use them. The captures on this page use the test provider, so the Twilio and MSG91 routes are not shown working here.Does it work on Odoo Enterprise?It depends on Point of Sale and SMS only and uses nothing from Enterprise, but the captures on this page were made on Odoo 20 Community. supportQuestions or a feature you need?Write to usBug reports, setup questions and ideas are welcome.odooaura@gmail.comAura Odoo TechMore Point of Sale, website and backend modules for Odoo.www.auraodoo.tech
Key Capabilities & Features
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
Screenshots & Previews
20 images availableExpand Preview
Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.