Automan FAQ

Neither label really fits. Automan is an operations and finance system for repair businesses and shops — the POS is just one part of it. Inside you get the repair workflow, inventory, purchasing, sales, returns, WhatsApp, reports, payroll, user access, and accounting, depending on which modules are active.

See the repair shop operations system

Automan’s core modules are free, with clearly stated daily transaction limits. Premium modules are activated with tokens or a subscription — only when your shop needs them. No countdown timers and no prices that change quietly.

Yes. A small shop does not have to use every module from day one. Start with the repair workflow, customers, receipts, status tracking, and basic reports. Other modules come later, when the shop starts needing advanced inventory, WhatsApp, payroll, promotions, or accounting.

Yes, and it does not have to happen all at once. Products and inventory can be imported from Excel using a template. For accounting, opening balances are set up through a wizard — no journal knowledge required first. Start with the most important data; the rest can follow as you go.

No, and we do not claim it is. Automan uses a non-official WhatsApp gateway. Available features: auto-sender, autoresponder, quick answers, targeted broadcasts, and 26 automatic reminders — with natural delays, sending-hour controls, and safe-usage guidance. We prefer explaining the limitations openly over promising “ban-proof”.

Read the safe WhatsApp guide

No — and we do not promise that. What runs automatically: VAT for tax-registered (PKP) shops on taxable transactions, and employee income tax (PPh 21). Other taxes such as PPh 23, PPh 22, PPh 4(2), Final UMKM, and PPh 25 are not automated yet, and we say so plainly.

See the accounting and tax boundaries

No. Every Store App uses its own dedicated database — your shop’s data does not share a room with thousands of other shops. Backups and an operational audit trail are available. To be honest: this is an architectural isolation claim, not a “leaks are impossible” promise — no system can promise that.

Yes. One account can create more than one Store App, each with its own subdomain and database. Worth knowing: centralized cross-branch consolidated reporting is not available yet — each shop is read from its own Store App.

Not yet — and we do not sell features that do not exist. Automan’s current focus is operational and financial depth you can inspect directly: repairs, inventory, returns, audit, payroll, WhatsApp, reports, and accounting.

Compare needs, not just feature lists

Lite reports help owners read channel balances, cash flow, receivables, payables, and profit and loss — without having to understand accounting. Accounting is for when the shop needs journals, a Balance Sheet, P&L, Cash Flow, period closing, and more formal reports for an accountant, a bank, or tax registration. Both read the same transaction data, so moving up does not mean starting over.

See repair shop accounting

Menus follow the installed modules, each module’s active period, and the user’s access rights. Check Module Setting, module status, the user’s group, and its permissions.

The most commonly recorded cause: an inaccurate device clock. Turn on automatic time synchronization on the device, then try logging in again.

The main transaction forms have anti-duplicate safeguards, such as transaction locks and duplicate checks. A safe habit on a slow connection: do not press save repeatedly — check the transaction list first before re-entering.

That is a risk-control mechanism, not an error. The system holds messages to contacts that have never interacted before (cold contacts) to protect the health of the shop’s number, then schedules them according to the rules.

The return value automatically offsets the remaining debt first. Only if there is an excess does it become a refund. The original transaction’s status is recalculated along the way — no manual recap.

See returns, claims, and corrections

Not necessarily. A damaged part that can still be claimed goes into Damaged Stock, then gets claimed to the supplier through the warranty claim flow. The item’s origin and the claim process are recorded, so a damaged part does not silently turn into a loss.

See returns, claims, and corrections

That is intentional. Once the unit is handed over, the job data is locked so the final record cannot change quietly. If something needs correcting, use the correction flow, which keeps its history.

Check in order: period filter, payment channels, return transactions, receivables/payables, cost of goods, and payment dates. Use the drill-down to source transactions where available — the difference usually shows up at one of those points.