Automan Settings Dictionary: What Each Menu Does
Settings are not a checklist of switches that all need enabling. Each section changes one of five things: master data, new-transaction defaults, process rules, customer-facing output, or reporting and journal records. Available menus also depend on installed modules and the account’s Access Permission.
Business Identity
| Menu | Purpose | Effect to verify |
|---|---|---|
| General | Store App language, timezone, country, and landing page. | Interface language, transaction timestamps, and the first page opened. |
| Store | Shop name, phone, address, logos, and brand assets. | Receipt and report headers. This page also contains Store Payment Channels for the shop’s cash drawers, bank accounts, and wallets. |
| Payment Channels | Provider master with Bank, Retail Outlet, Wallet, or Cash types. | Supplies choices when creating a Store Payment Channel. Do not enter only the shop’s account number in this master. |
A Store Payment Channel is a transaction’s money pocket. The selected channel is stored by supported repair, purchase, sale, settlement, return, expense, payroll, cash-transfer, asset, and tax flows. When Accounting is active, the account mapping on a channel determines the cash or bank account used by journal entries.
Users And Partners
| Menu | Purpose | Effect to verify |
|---|---|---|
| Pengguna → List | Create and maintain staff accounts. | Who can sign in and which staff identity is recorded on transactions. |
| Users → Type | Group roles such as admin, cashier, or technician. | Basis for data restrictions and Access Permission. |
| Partners → Customer Type | Group customers. | Type choices on customer masters and segmented data. |
| Mitra → Kategori Pemasok | Group suppliers. | Category choices on supplier masters and purchases. |
| Partners → Vendor Category | Group vendors. | Category choices on masters or transactions that use vendors. |
Creating a user type does not grant permissions by itself. Configure its matrix again under Settings → Access Permission before staff use the account.
Transactions
| Menu | Purpose | Effect to verify |
|---|---|---|
| Currency | Symbol, symbol position, decimal length, and decimal/thousand separators. | Amount display on forms, receipts, and reports; it does not rewrite old transaction values. |
| Courier | Courier master and support for tracking or international-rate checks. | Courier choices in supported delivery flows. |
| Purchase → Transaction | Default delivered, paid, payment method, and tax values. | Initial values of each new purchase; the operator must still confirm the real transaction. |
| Sales → Transaction | Default payment method, tax, paid, delivered, and show-capital values. | Initial sales/POS values and capital visibility in product pickers. |
| Sales → Note | Title, standard/thermal printer, 58/80 mm size, logo, signatures, and extra information. | Printed sales receipt. |
| Expense → Category | Expense types and expense-account mapping. | Report grouping; the mapped expense account receives journal entries when Accounting is active. |
| Expense → Unit | Expense units and one default unit. | Initial unit in expense details. |
| Payroll | View mode, profit sharing, calculation trigger, and payslip content. | Payroll-list privacy, profit-share calculation, and printed payslips. |
Repairs
| Menu | Purpose | Effect to verify |
|---|---|---|
| General | Queue rules, automatic work selection, view mode, notifications, warranty timing, contact masking, and permissions to add/change services or parts. | Technician workflow, staff-visible data, warranty dates, handover flow, and related report calculations. |
| Item Type | Repair-unit types and new/warranty receipt codes. | Item-type choices and generated repair-unit codes. |
| Service | Service master, price, item type, and warranty period. | Service choices, customer charges, and warranty dates. |
| Status | Process/Confirm/Final stages, sequence, work threshold, allowed transitions, and notifications. | Technician flow, valid next statuses, and customer status messages. |
| Kriteria SAW | Three weighted criteria with Kode, Nama, Terjemah and Bobot columns. Defaults: intake time (weight 20), customer type (45), and fault type (35) — 100 in total. | Work order when the queue uses the SAW method. Note the defaults: customer type outweighs arrival time, so a priority customer can jump ahead of somebody who came earlier. Raise the intake-time weight if your shop wants strict first-come order. |
| Receipt Note | Printer, title, logo, QR, checklist, phone masking, information, and terms. | Intake receipt. The QR code points to public repair tracking. |
| Deliver Note | Printer, service/part details, costs, warranties, discount, checklist, phone masking, and statement. | Handover receipt when the unit is collected. |
| Repair Track | Visibility of repair cycle, checklist, services, parts, costs, and login button. | Information customers can see on the public tracking page. |
Customer Contact Censored under Repairs → General leaves the last four digits visible to non-admin accounts in supported repair and sales views. The customer-number masks on Receipt Note and Deliver Note control only their respective printed outputs; these are three separate controls.
Inventory
| Menu | Purpose | Effect to verify |
|---|---|---|
| Inventory Management | Flexible/Sequential search, Fifo/Average ICM, purchase-shipping allocation, and COGS visibility for non-admins. | Product search, cost in flows that implement it, stock cards, and COGS disclosure. |
| Asset Category | Fixed-asset categories. | Asset grouping and related accounting mapping when its module is active. |
| Category, Subcategory, Brand | Product-classification masters. | Filters and choices in product masters. |
| Unit, Dimension Unit, Variant Name | Product-unit and variation masters. | Product-master fields, unit conversion, dimensions, and variants. |
The Inventory Costing Method selector offers Fifo or Average. The current source applies the method in several spare-part and interstore-transfer paths, while the main sales/POS flow still consumes the oldest stock lot. Because application is not uniform, this guide does not promise that choosing Average automatically averages COGS across every transaction and report.
Modular And Sensitive Menus
| Menu | Purpose | Effect to verify |
|---|---|---|
| Promotion & Point | Condition/benefit masters and point-earning rules. | Promotion and point evaluation on supported transactions; visible when its module is active. |
| Accounting → GL Setup | Finance, chart of accounts, periods, default accounts, cash/bank mapping, and journal-event mapping. | Automatic journals and financial reports. Do not change live mappings without a posting test. |
| Accounting → Taxation | Tax rates, PTKP, and employee tax profiles. | Tax calculations and records that use these masters. |
| WA Gateway | The Store App’s WhatsApp session connection. | Manual or automatic messages that require an active gateway. |
| Queue Screen | Customer-display configuration. | Queue information shown on the public/customer display. |
| Access Permission | Menu and action permissions by user type. | Menus, data, and operations available to staff. |
| Copy Products & Settings | Copy supported data between Store Apps. | Destination data; verify source and target before running it. |
| Backup & Restore | Create and restore backups. | All Store App data at a backup point. Back up before a reset or large import. |
| Activity Log | Application change history. | Who changed what when Log Activity is active. |
| Restore Log | Restore-process history. | Review of restore time and outcome. |
| Reset Data | Delete selected data groups through the reset panel. | Destructive; never treat it as routine cleanup. Back up and verify the target first. |
Use the safe order: backup → change one setting → run a test transaction → inspect receipts/public pages → inspect reports or journals → make the next change.
Before you start
- The minimum setup and basic master data are complete.
- Logged in as owner/admin; visible menus depend on installed modules and account access.
Steps
-
Identify the available menus before changing anything
Open Settings and match the visible branches with the map below. Store App menus follow installed modules and Access Permission, so not every shop sees Accounting, Promotion & Point, WA Gateway, Queue Screen, Interstore, Backup & Restore, or Activity Log.
Visible menus follow installed modules and account access. -
Complete the shop's identity and money pockets
Review General and Store, then manage cash drawers, bank accounts, or wallets in the Store Payment Channels section on the Store page. Payment Channels is the provider-type master; it is not the primary place for entering accounts owned by the shop.
Accounts and money pockets owned by the shop are managed on the Store page. -
Set transaction defaults and their printed outputs
Configure Currency, Purchases, Sales, Receipts, Couriers, Expenses, and Payroll to match the real workflow. Defaults prefill new transactions; receipt settings change printed output, while categories mapped to accounts affect journal entries when Accounting is active.
Transaction defaults and printed outputs are configured separately. -
Configure repair flow, privacy, warranties, and tracking
Under Repairs → General, review queue ordering, workflow visibility, contact masking, warranty start dates, and cost-change permissions. Configure Receipt Note, Deliver Note, and Repair Track separately because each controls a different customer-facing output.
Changes here can affect staff, customers, and reports. -
Configure inventory before stock transactions become busy
Under Inventory → Inventory Management, review search behavior, Inventory Costing Method, purchase-shipping allocation, and COGS visibility. Run one test purchase and one test use or sale, then compare the stock card and reports before using the settings on production data.
Test cost and stock effects before operations become busy. -
Restrict sensitive menus and test one change at a time
Limit Settings, Access Permission, Accounting, Backup/Restore, and Reset Data to owners/admins. After changing one option, test the affected transaction form, receipt, report, and public page; record the result before changing another option.
Sensitive menus should be available only to owners or admins.
What you end up with
Each Settings branch is understood by function and effect, while money, inventory, privacy, warranty, access, and data options are tested before live operational use.
If something goes wrong
A menu mentioned in this guide does not appear
Check that its module is installed and active, then check the account's Access Permission. Store App menus intentionally change with both conditions.
Payment channels exist, but the shop's account is unavailable in transactions
Open Settings → Business Identity → Store and fill the Store Payment Channels section. The Payment Channels master only defines provider types such as bank, wallet, retail outlet, or cash.
A customer number is still visible in a particular output
Customer Contact Censored under Repairs → General limits non-admin views. The masks on Receipt Note and Deliver Note are separate options; check all three for the outputs you need to protect.
COGS or profit changed after switching the inventory method
Stop further changes and compare a test purchase, stock card, spare-part use, sale, and reports. Do not switch methods repeatedly on an active shop without reviewing the data and reports.
A setting changed without the owner knowing
Restrict the menu through Settings → Access Permission. If Log Activity is installed, inspect the change through Settings → Activity Log.
Related tutorials
- Tutorial
Minimum Setup before the First Repair
The minimum identity, admin account, and money-pocket setup.
- Tutorial
Setting Cashier and Technician Access Rights
Restrict menus and actions by role.
- Tutorial
Back Up Data before a Reset or Big Import
Protect data before risky changes.
- Feature
Repair Shop Operations System
The larger system affected by these settings.