OneXEOS
FAQs

FAQs

OneXEOS is built to flex for any size - from brand-new startups to SMEs with hundreds of staff. Whether you run one store or a chain of 50 branches, OneXEOS handles it on a single unified platform with no extra software required.

Yes. OneXEOS supports bulk imports from Excel and legacy systems, and our team helps you migrate menus, products, customers and branches.

Absolutely. OneXEOS connects with leading marketplaces, e-wallets, banks, shipping carriers and e-invoice providers, with open APIs for anything else.

One transparent price unlocks the full ecosystem - no hidden fees and no feature limits.

You get free onboarding to import your data and train your team, plus 24/7 technical support whenever you need it.

Yes. Products, stock, customers and receivables live on one platform, so closing an order decrements stock and books the financials immediately - nothing to sync between separate systems.

Yes. Define price lists by location, channel or customer group, with volume discounts and time-boxed promotions; the right price is applied automatically when the order is raised.

An approved quote converts straight into a sales order with no re-keying, keeping the agreed prices and staying attached to the customer and the conversation history.

You can. Each rep has their own customers, orders and targets, and reporting rolls up by rep, channel and location continuously.

Yes. It keeps selling and stores orders locally, then syncs every order and stock movement back the moment the connection returns.

It can. Part cash, part card or QR is recorded on the same bill, and the end-of-shift report separates each method.

The till screen is built so a new hire is comfortable within about half a day; everything used often is on the main screen.

Yes. Each shift records who opened and closed it and the float at both ends; the system reconciles against cash takings and flags the difference.

No. Scanning at the table opens the menu in the browser; they choose and send it to the kitchen without installing anything.

Yes. Split by dish or evenly by headcount, and merge several tables into one bill before payment.

Each dish carries a recipe and quantities; selling the dish decrements exactly those ingredients and flags anything below its reorder level.

It does. The kitchen screen runs in a browser, so a tablet, a touchscreen or an existing kitchen PC all work.

Yes. Leads from website forms, ad campaigns, the phone and social channels collect in one place and are assigned by the rules you configure.

It does. Orders, balances and loyalty points show on the customer record, so a rep never has to open another system.

Yes. Permissions work by role and team - managers see everything, reps see the customers assigned to them.

You set rules on time since last transaction, renewal dates or pipeline stage; the system raises a task for whoever owns the account.

Yes. Points sit on one customer account, so earning at the counter and redeeming online - or the other way round - both work.

Yes. Every code carries eligibility conditions, an expiry and a usage limit, all checked at the payment step before it applies.

Zalo, SMS or email as configured, targeted at the segment you choose by buying behaviour, time since last visit or birthday.

Yes. Each campaign reports how many were reached, how many came back and the revenue produced, so campaigns can be compared.

Through a 24/7 online page, over Zalo, or entered by staff at the counter. Every channel writes to the same diary, so a taken slot never shows for the next person.

Slots are held against both the time and the assigned staff member, so two customers cannot book the same person in the same window.

Each package shows sessions used and remaining, draws down at every visit, and flags when it is nearly exhausted so you can reach out first.

At the lead time you configure - typically a day before and again a few hours before - over SMS or Zalo depending on which channels you enable.

Yes. Both read the same inventory, so selling out on one channel closes the other immediately - no telling a customer you're out after they've ordered.

No. You pick a template and edit layout, catalogue and content pages in the system; a developer is only needed for deeper customisation.

The gateways and e-wallets commonly used in Vietnam all connect; whichever you enable appears at checkout.

They are. Website orders join the same workflow as counter orders, so the operations team watches a single list.

Shopee, Lazada and TikTok Shop connect directly, alongside your own online store. Products, prices, stock and orders all run off one source of data.

Yes. An order on any marketplace decrements stock immediately and pushes the remaining quantity back out to the others, which is what keeps you from overselling during a flash sale.

Per order: cash collected by the carrier, marketplace fees, shipping and promotions are matched back, and anything that doesn't line up is flagged for you.

A single storefront is usually connected and synced within one working day; sellers across several marketplaces are phased so trading is never interrupted.

Yes. Every channel reads the same inventory, so selling out on one closes the others immediately.

You can. Goods are received by batch with their own expiry; the system warns early and picks the nearest-expiry batch first.

A barcode scanner, or just a phone camera. Count by zone and record variances with a reason and the person who made them.

Yes. Every movement records the person, the time and the related document, so unusual numbers can be traced back.

Current stock, minimum levels, recent sales velocity and each supplier's lead time.

Yes. Configure thresholds and the matching approver; each step records who approved it and when.

You can. The order records each receipt and stays open on the shortfall until it is complete or you close it.

Invoices attach to their order and goods receipt; the system tracks due dates and consolidates the payment schedule by period.

It takes each product's BOM, the orders you hold and current stock to work out the shortfall, then proposes purchase orders against each supplier's lead time.

Yes. Keep multiple versions to compare cost and quality, and choose which applies to each work order.

To the batch: input materials, process steps, the shift that ran it and its quality results are all attached.

Machine data can be entered per shift by hand, or collected automatically over IoT where the equipment supports it - both feed the same dashboard.

A phone, a tablet or a PC at the line. Check sheets open by process step and take results with photos and notes.

The batch is separated and locked so it cannot move downstream; rework, downgrade or scrap goes through an approval step.

Yes. Records attach to the production batch - criteria, results and inspector - and export in minutes on request.

Statistics by defect type, process step and shift show what keeps recurring, which points at where the process needs changing.

Yes. Invoices are issued to the current e-invoice standard, sent to the customer and archived for the required retention period.

You can. One invoice accepts several payments, and the system tracks the remaining balance and its due date.

Yes. Reporting filters by location or consolidates across the group, off the same underlying data.

It does. Data exports in a format the common packages import, or you can use the Accounting app in the ecosystem directly.

Vietnamese Accounting Standards (VAS). Businesses reporting in parallel under IFRS get that configuration set up during rollout.

From sales, purchasing, stock movements and cash in the system; accounting reviews and adjusts only where needed.

Yes. A locked period accepts no new entries; adjusting entries go through approval and keep their own trail.

You can. Financial statements and the required forms export by period, with the underlying detail available for reconciliation.

No. Flows are built in a drag-and-drop interface by department, seniority and value threshold, and can be changed at any time.

Delegate temporarily to someone else for a set period; the log still records who approved on their behalf and when.

Yes. The system reminds whoever holds the request past the turnaround you configure, and escalates if it stays unactioned.

The full history stays with the request, including rejections and requests for more information, for later reference.

No. Choose measures, filters and groupings in the interface; the report is saved for reuse.

Dashboards read operational data directly, so they update in real time rather than waiting on a batch sync.

Yes. Permissions work by role and scope - location, department or product group - so each person sees only their own area.

You can. Export to Excel or CSV, or connect over API to whatever BI tool you already use.

The LoRaWAN version has a maximum range of 15 km, suited to continuous monitoring of farms covering hundreds of hectares and of difficult terrain.

The all-in-one handheld meter returns 9 readings in just 5 seconds, right in the field. It connects directly to a smartphone over Wi-Fi or Bluetooth and charges over USB Type-C.

It measures 9 indicators: nitrogen (N), phosphorus (P), potassium (K), pH, moisture, soil temperature, electrical conductivity (EC), salinity and total dissolved solids (TDS), so you can optimise fertiliser, water and the root zone.

OneXIoT monitors soil, water and air: soil nutrients and chemistry, the salinity and quality of irrigation water, and cameras that follow crops, shrimp and fish, even in murky water.

They run on solar power or charge over USB Type-C, which avoids running cables out to fields and ponds.

The heavy-metal meter detects lead, mercury, arsenic and cadmium using the SWV method, with results in about 10 minutes.

They take scheduled photos or stream live video so you can follow crops, shrimp and fish remotely, even in murky water. The cameras run on USB Type-C or solar power.

The OneXIoT team surveys your farm, recommends how many devices you need and where, installs the LoRaWAN stations and sensors, connects the data to the platform and shows you how to follow it on the dashboard. The exact schedule is agreed after the survey.

Clocking devices, a mobile app with location, or manual entry for exceptions - all three feed the same timesheet.

Yes. Define base pay, allowances, bonuses and deductions the way your business already works, reused every period.

They do. Contribution rates and tax bands follow current regulation, and you review before closing the period.

Yes. Each employee sees their own payslip, worked days and leave balance, and nobody else's.

Kanban, list, calendar or project timeline - the same data, in whichever view suits how your team works.

Yes. Time is recorded per task and rolls up to the project so actual cost can be compared with the estimate.

They are. The system reminds the owner ahead of the date and marks overdue work on the team board.

Yes. Tasks can be attached to the related customer, order or approval request, so context isn't scattered.

No. Pick a trigger, add conditions and actions in a drag-and-drop interface; code is only needed for complex API calls.

New orders, status changes, stock reaching its reorder level, contracts or appointments falling due, and hourly, daily or monthly schedules.

Yes. Flows call third-party APIs, and inbound webhooks can trigger actions inside OneXEOS.

The log records each run with its result and failure reason; you are notified and can re-run it manually.

Yes. Search covers content as well as filenames and tags, so the exact title isn't needed.

They can. The edit history keeps each version, shows the differences and restores an earlier one on request.

Through the approval flow you configure; once approved, the document records its effective date and approver and supersedes the previous version.

Yes. Documents marked sensitive keep an access log of who viewed them and when.

Files belong to the business, not a personal account. Revoke access and the data stays in the department folder.

Yes. Each link carries an expiry, an optional password and view-only or download rights, and can be revoked at any time.

They can. Deleted files sit in trash for a retention period before permanent removal, and earlier versions can also be restored.

Yes, on folders marked sensitive - the system records who viewed or downloaded a file and when.

Only what the person asking is permitted to see. The account's permissions apply to the assistant unchanged.

Yes. Each answer carries its source figures and a link to the underlying report so you can check it.

You define the scope it answers within; beyond that it hands the conversation to a person rather than guessing.

No. Operational data is used only to answer within your business and is not fed into shared model training.

No. Each unit carries its own status and locks as soon as a booking or contract is raised, so two deals cannot hold it.

They are. Invoices generate per period from the contract, the system prompts on due dates and records partial payments.

Through whichever channel you enable - an online form or Zalo; the request opens a task for the technical team with an owner and progress.

Yes. Occupancy, revenue, receivables and operating cost filter by project, by building or consolidated.

At the lead time you configure per contract type; the system raises a task for the owner rather than only sending a notification.

An addendum attaches to the original contract and preserves its history, with changed terms recorded for later comparison.

It is. The collection schedule comes from the contract terms, tracks each instalment and records partial payments.

Yes. Permissions work by department and sensitivity, and flagged contracts keep a log of who viewed them.

POSCRMInventoryKDSStaffReportsAI Menu

Ready to upgrade the operating system for your business?

You are ready to upgrade the operating system for your business in about 5 minutes. You create an account, pick your industry and switch on the apps you need, with the core plan free forever. No credit card and no long-term contract. You can add a branch at any point. Everything you turn on shares the same 1 data layer.

OneXEOS FAQ - pricing, data migration and support