# TUKO — full content > Run your business. Know what to do next. > > The complete TUKO Learn expert archive as plain text — one fetch gives > an agent the whole corpus. Index and licensing: https://tukohq.com/agent/ ## Your Best Seller Might Be Losing You Money URL: https://tukohq.com/learn/best-seller-not-profitable.html ## Sales ≠ profit A product selling 100 units at a ₱5 margin earns you ₱500. A product selling 20 units at a ₱60 margin earns you ₱1,200 — on a fifth of the work. Owners feel the first one: the shelf keeps emptying, the staff stays busy, the till sounds busy. The second one barely registers. Most small businesses can tell you their best sellers instantly. Far fewer can name their most profitable products. The two lists are rarely the same. ## How a popular product quietly loses money - Cost creep. The supplier raised the price twice this year — the shelf price never moved. Every sale earns less than the last, and nobody recalculated. - The unpriced discount. "Suki" discounts, free delivery, a thrown-in extra — each one small, none of them counted against the product's real margin. - Shrinkage written off. Spoilage, breakage, and losses get absorbed silently. The product's true cost includes what you threw away, not just what you sold. - Busy-work pricing. Low margins on labor-heavy items mean the team spends its best hours on the least profitable work. ## And then there's the opposite problem: dead stock While the best seller gets watched, dead stock gets ignored. Units that haven't moved in 90 days aren't neutral — they're cash frozen on the shelf, space a better product could use, and a reorder budget spent on the wrong thing. Most shops could free a month's worth of capital just by stopping the reorders nobody audited. ## Read margin, not just volume This is what connected records change. When every order carries the real product cost and every expense hits a ledger, reports stop describing sales and start describing profit — which products earn, which just move, and which have quietly gone negative. Expense tracking closes the gap between "sold for ₱150" and "kept ₱12." And the fix is practical, not academic: - Reprice the creepers. Products whose cost outgrew their price — the easiest profit you'll ever find. - Push the real earners. Shelf position, bundles, and staff suggestions toward the products that pay. - Stop restocking ghosts. Slow-moving stock shows up before it becomes dead — reorder by movement, not by habit. More on how TUKO reads margins for shops, or try it free. Questions — support@tukohq.com. ## Business Pulse vs Dashboards — Decisions, Not Charts URL: https://tukohq.com/learn/business-pulse-vs-dashboard.html ## What a dashboard asks of you A dashboard is honest about everything and helpful about nothing in particular. It shows revenue, stock counts, open invoices, and headcount side by side — then waits for you to figure out which tile changed, which change matters, and what to do about it. That's fine work on a quiet afternoon. It's expensive work at 7:40 in the morning before the shop opens. The cost isn't the dashboard itself — it's the interpretation tax: every day, you re-derive "what needs attention" from raw numbers, and some days you get it wrong or run out of time before the invoice that was 12 days overdue becomes 30. ## What a pulse does instead A business pulse inverts the flow. Instead of you scanning the data, the system scans it — then shows you a short, ranked list of what it found: - It detects. Deterministic checks run over your real records — orders, payments, inventory, purchase orders, expenses, payroll, attendance — looking for known patterns: an invoice past due, a product about to stock out, a regular who's gone quiet. - It prioritizes. Findings are ranked onto a single card — the top things needing attention, not a feed of everything that happened. - It hands you the action. Each signal carries its evidence — the actual numbers — and a recommended next step, so the path from "noticing" to "doing" is one tap. Dashboards answer "what is happening?" A pulse answers "what needs me?" ## Where each one wins This isn't dashboards-are-bad. Each tool wins in a different moment: - Pulse wins for triage. Morning check-ins, catching problems early, knowing where to start. Thirty seconds, not thirty minutes. - Dashboards win for exploration. Month-end review, spotting a slow trend no single threshold would catch, answering a question nobody wrote a detector for. The failure mode to avoid is using a dashboard for triage — because the day you skip the scan is the day the stockout, the drifting customer, or the overdue invoice slips through. A pulse doesn't get tired, and it runs even on the mornings you don't. ## How TUKO's Business Pulse works Business Pulse is TUKO's intelligence layer, and it's deliberately un-magical. Detectors — ordinary rules, not a black box — scan your business data across 30 signal types: overdue invoices, low stock and stockout risk, slow movers, expense spikes, supplier delays and price increases, customers due to reorder or going quiet, payroll pressure, unusual absences, and "outside your normal" days measured against your own trailing 84-day baselines. The results land on the Business Pulse card in the Command Center, ranked. Every item shows its numbers — the amount, the days, the count — and offers a concrete action: open the record, create a task, record a payment. You dismiss, snooze, or act; the list stays short. An optional decision-model enrichment can re-rank the top items — and TUKO is honest about the mechanics: it's off by default, sends only minimized numbers and categories (never names or notes), falls back to standard ranking whenever it's unsure, and logs every evaluation so it's auditable. Whether it's on or off, the pulse you see is grounded in your records — estimated values are always labeled "est." One more thing worth knowing: the pulse learns your normal, not an industry's. "Unusual" is measured against your own trailing 84-day baselines, so a sari-sari store and a machine shop each get judged by their own rhythm. And if you ever wonder why something surfaced — or how a feature works — every workspace ships a built-in Help Center with searchable articles and quick guides, under the ? icon in the top bar or Help in the sidebar. Reports and dashboards stay underneath, unchanged. Business Pulse just means you check them because you want to — not because it's the only way to find out what broke overnight. ## Can Your Business Run a Week Without You? URL: https://tukohq.com/learn/business-runs-without-you.html ## The owner is the system Prices live in your head. Supplier numbers are in your phone. Customer balances are "something you remember." Every unusual question routes to you, every approval waits for your reply, every day off becomes a working day. You didn't build a business that depends on you — you built one where you are the database. It works, until it doesn't. The ceiling isn't effort or headcount. It's that the business's memory is stored in exactly one person. ## What breaks first - The questions stop getting answers. "Magkano 'to?" — and the price is in your head, unreachable. - Decisions queue up. The reorder, the refund, the discount request — parked in a chat thread until you're back. - The records drift. Sales happen without their paper trail. You return to gaps you'll never fully reconstruct. - You come back to surprises. And the unspoken lesson: don't leave again. ## It's not a people problem The usual answer — "hire someone I can trust" — misses the point. Good staff can't answer questions whose answers aren't recorded anywhere. Trust doesn't give your cashier a way to check whether Mrs. Reyes already paid, or how much stock is left in the back. Delegating without a system doesn't remove you; it adds a phone call. ## What a business that runs without you is made of - Records staff can reach. Prices, stock, balances, order history — looked up, not remembered. In TUKO every customer has a full profile with orders, balances, and notes, readable by whoever needs it. - Permissions, not guesswork. Staff see and do what their role allows — a cashier sells, a manager approves — so delegation doesn't mean handing over the keys. - The day that reports to you. The daily brief puts what matters — overdue balances, low stock, stalled orders — in front of you wherever you are. You check in by choice, not by necessity. - A trail for everything. Refunds, voids, and price changes are recorded with who and when — oversight without hovering. ## The real payoff A business that can run a week without you is also the one that can open a second location, take on a partner, or get sold someday. Independence from the owner isn't just a vacation benefit — it's the difference between owning a job and owning an asset. Start with the record-keeping, and the rest follows. Try TUKO free — questions to support@tukohq.com. ## Why a Busy Shop Can Still Run Out of Cash URL: https://tukohq.com/learn/cash-flow-busy-shop.html ## Busy doesn't mean liquid This is the most confusing thing about running a small business: you can be profitable and still run out of cash. The sales are real. The problem is timing — the money you earned isn't in the register yet, while the money you owe already left. When the cash isn't visible day by day, every short week feels like bad luck. It isn't luck. It's a pattern you can see coming. ## Where the cash actually went - It's owed to you. Utang and unpaid invoices are revenue on paper — not cash you can spend. A good sales week can mean a record-high receivables week. - It's sitting on a shelf. Every peso in unsold stock is a peso not in the till. Over-ordering feels like preparation; it's really a cash withdrawal. - It slipped out quietly. Delivery fees, packaging, a refill here, a "small" purchase there — expenses that never hit a ledger still hit the drawer. - The timing never lined up. Suppliers want cash on delivery; customers pay you Friday. You cover the gap out of your own pocket — every cycle. ## Looking backward doesn't help Most owners find out they're short when they're already short — checking the drawer, not the future. A month-end report explains last month's problem. It can't warn you about next Thursday. What's needed is the opposite view: not "how did we do" but "will there be enough." ## The five-minute habit that fixes most of it In TUKO, that view is Cash Flow Foresight — a day-by-day projection built from your real records: money coming in, money going out, and the day the line crosses zero if nothing changes. When a short day is coming, you get warned while there's still time to act — collect the 30-day balance first, hold the non-urgent purchase, split the supplier payment. Two habits make the projection honest: - Record every expense the day it happens. Expense capture takes seconds — skip it, and the forecast is optimistic fiction. - Keep balances current. Receivables are real cash-in once collected — aging shows which ones to chase first. ## When you can see it coming, it stops being a crisis A short week you saw ten days out is a scheduling problem. The same week discovered on the day is a loan you didn't want to take. The math doesn't change — only when you learn it. See how Cash Flow Foresight works, or try it free. Questions — support@tukohq.com. ## How to Track Customer Credit (Utang) Digitally URL: https://tukohq.com/learn/customer-credit-utang.html ## The problem isn't utang — it's the notebook Store credit — utang — is a competitive feature, not a flaw. Customers choose the shop that lets them pay Friday. The losses don't come from extending credit; they come from tracking it in places that forget: a notebook that gets wet, a chat thread that scrolls away, a mental note that fades. The fix isn't refusing credit. It's making the ledger automatic. ## What goes wrong with informal tracking - Disputes with no record. "Bayad na ako nung Martes" — and nothing to check against. - Silent growth. Balances creep up ₱200 at a time until collecting feels awkward. - Aging blindness. All utang looks equal — until you realize some of it is 90 days old. - Owner dependency. Only you know who owes what; you can't take a day off. ## The digital version of the same trust In TUKO, credit isn't a separate system — it's what happens automatically when a customer takes an order without paying in full: - Every order carries a balance. The sale is recorded once; the unpaid amount is the balance — no second ledger. - Payments reduce it. Record a bayad of any amount — full or partial — and the balance updates instantly. - Aging is automatic. You see each outstanding amount and how many days it's been there — so you follow up the 45-day ₱3,000 before the 2-day ₱150. - The customer record has context. Full order history, payment pattern, and notes — so the conversation starts with facts, not confrontation. ## Collections without the awkwardness Knowing the number changes the conversation. Instead of "para kay alam ko may utang ka" (because I remember you owe), it's a fact both sides can see. Overdue balances also land on your daily brief — collection becomes a five-minute morning habit instead of an end-of-month confrontation. Read more on payment and receivables tracking or customer management in TUKO — or try it free. ## How Much Does ERP Software Cost a Small Business? URL: https://tukohq.com/learn/erp-cost-small-business.html ## Why traditional ERP cost so much The license was never the whole price. Legacy ERP pricing hid its real cost behind three layers: - Implementation. Consultants to configure it — often a months-long project costing multiples of the license. - Customization. Workflows built for enterprises, so everything had to be tailored down. - Maintenance. Upgrades, IT staff, and the ongoing cost of keeping a complex system alive. Small businesses weren't priced out of the software — they were priced out of the project around it. ## What changed The cloud removed the servers and IT staff. A new generation of all-in-one apps — built for small businesses from the start — removed the implementation project entirely. The cost model became a plain subscription, often with a free starting tier, sized to teams of 2–50 rather than 2,000. TUKO goes a step further: the complete core system is free — no subscription at all. TUKO is in that generation: sign up and the app works today, free, no consultant required. ## The cost nobody puts on the invoice The more dangerous number isn't the subscription — it's the integration tax. When tools don't connect: - Attendance gets re-typed into payroll - Orders get re-entered into the stock sheet - Customer balances get reconciled by hand Every week, that's hours of skilled owner time — the spreadsheet tax, just wearing subscriptions. An all-in-one app eliminates it by construction: there are no integrations because there are no separate tools. ## A better question to ask Not "what does it cost?" but "what does it cost when it works?" A cheap tool that leaves you reconciling five copies of the truth is expensive. A modestly priced one that makes re-entry disappear is cheap. Evaluate total cost as: subscription + implementation + the hours you'll spend keeping copies in sync. ## Missing Stock & Short Registers — Without Accusing Anyone URL: https://tukohq.com/learn/missing-stock-shrinkage.html ## Shrinkage is normal. Not knowing is the problem. Every business that holds stock and takes cash loses some of both. Suppliers short a delivery, items break, a sale gets rung up wrong — and yes, sometimes a hand goes in the till. What's corrosive isn't the loss itself; it's guessing. You don't know how much is missing, where it went, or whether it's a mistake or a pattern. That uncertainty is what owners carry home at night — not the ₱400, the not-knowing about the ₱400. ## The three ways shops usually handle it - Suspect everyone. Morale dies, good staff leave, and the actual leak continues — because suspicion never found it. - Shrug and absorb it. Write it off as "ganyan talaga" — and watch the write-off grow every year. - Buy a camera. Which only ever shows you a replay of the loss after it already happened. None of these answer the real question: where, exactly, is it going? ## Design the leak out instead The fix isn't surveillance — it's that every peso and every unit leaves a record, so missing things surface as facts, not vibes: - Register sessions per cashier. The POS opens and closes each shift with its own drawer. Cash variance is measured per session — "the drawer was short ₱400 on Tuesday's shift" is a fact, not an accusation. - Permissions per action. Refund, void, discount, and cash payout are separate permissions. A cashier can't quietly refund their own drawer — the system simply doesn't let them. - An audit trail for the sensitive stuff. Every gated action lands in a trail: who, what, when, and on which terminal. You review it when a pattern matters — not after a rumor. - Stock counts that tie to orders. Inventory decrements the moment an order is placed, so a count that's off is a real discrepancy — worth checking — not a spreadsheet that was never updated. ## Accountability without accusation Here's the underrated part: records protect honest staff too. When a short drawer or a missing case has a paper trail, the conversation is about the numbers — never about character. Patterns surface on their own, honest mistakes get fixed by training, and the rare real problem becomes undeniable on its own evidence. Most importantly, most leaks stop before they start. People behave differently when the till has a name and a count — accountability designed in beats suspicion applied after. See how the register works and photo-verified clock-ins, or try TUKO free. Questions — support@tukohq.com. ## POS System Without Internet: How Offline POS Actually Works URL: https://tukohq.com/learn/offline-pos.html ## What "offline POS" actually means An offline POS is a point-of-sale system that keeps taking sales with no internet connection. Not "mostly works" — works: ring up items, take cash, print the receipt, close the shift. The sale is recorded on the device itself and delivered to your records later. That's a much stronger promise than most cloud POS apps make. A typical cloud POS is a website — when the connection dies mid-sale, you're staring at a spinner while the queue at your counter grows. In the Philippines, where a brownout or a weak pocket Wi-Fi signal is a normal Tuesday, that's not an edge case. It's the use case. ## How a real offline POS works Under the hood, a genuine offline POS does four things — and each one has a wrong version you should watch for: - It queues durably. Every sale is written to storage on the device — not held in memory. Close the app, restart the PC, lose power: the queue survives. A POS that keeps unsent sales in a browser tab loses them the moment the tab does. - It keeps real timestamps. The 3:14 PM sale is recorded as 3:14 PM — not re-stamped to whenever the internet came back. Your daily totals, cut-offs, and payroll math depend on the time the sale actually happened. - It replays without duplicating. Each queued sale carries an idempotency key — a unique "don't post me twice" tag — so retries on a flapping connection can't charge the same sale twice. This is the part cheap "offline modes" skip. - It parks problems instead of dropping them. A sale the server can't place cleanly — say, a product was removed while you were offline — is set aside for a manager to review, never silently deleted. You should always be able to see what's queued and what parked. ## What still needs a connection Honesty check: offline isn't magic. The register needs to prepare while the connection is good — your catalog, prices, terminal settings, and staff list get saved to the device ahead of time. Sign in and open the register once while online, and the PC is ready for anything. Card and e-wallet payments still need the network to authorize — offline selling is cash-and-recorded-credit territory. And none of the queued work reaches your reports until the link returns. ## Why a desktop app, not a browser tab Browsers can't do durable offline money operations — a tab is rented memory on someone else's session. A real offline POS needs an installed app that owns storage on the machine. That's exactly what TUKO for Windows and TUKO for Mac are: the register and the attendance kiosk running as a desktop app, queueing sales and clock-ins on the computer itself and syncing when the connection returns — same POS, same workspace, same records. ## How to Stop Buddy Punching with Photo-Verified Clock-Ins URL: https://tukohq.com/learn/photo-verified-clock-ins.html ## Why attendance fraud is so cheap to commit Most small-business timekeeping runs on one of three things: a paper logbook, a shared PIN or card, or an honor-system app. All three fail the same way — they record what was claimed, not who was there, when: - Buddy punching: a co-worker signs, taps, or clocks in for someone who isn't there yet — or isn't coming at all. - Edited device clocks: if the phone's clock is the source of truth, the phone's owner controls the record. - After-the-fact edits: a log that can be quietly rewritten can't settle a dispute. None of this needs to be dramatic to cost you. Ten invented minutes a day across a small team is real money by the end of a pay period — and it lands silently in payroll. ## What photo-verified clock-ins change A photo-verified clock-in attaches a quick photo to each punch. That one addition flips the economics of attendance fraud: - Deterrence beats detection. People don't buddy-punch when they know every punch carries a face. You rarely need to check the photos — their existence does the work. - Evidence, on demand. When a timesheet looks wrong, a manager opens the photo evidence for that punch instead of interviewing half the floor. - No new hardware. It uses the phone the employee already has — no fingerprint terminals, no badges to lose, no kiosk to maintain. ## The other half: a clock employees can't set Photos prove who; the timestamp proves when. Both need to be out of the employee's reach. The fix is to stamp punches on the server, not the device — a punch records the server's time when it arrives, so changing the phone's clock does nothing. The device time can be kept as diagnostic context (a big gap between the two is itself a signal), but it should never become the official record. ## Do it fairly Photo timekeeping touches employee privacy, so the how matters as much as the what: - Tell people. Employees should know photos are taken at clock-in, why, who can see them, and how long they're kept. - Scope access. Photos should live in private storage — visible to the employee and authorized managers, not on a public link, not browsable by the whole team. - Make it a policy, not a mandate. Require photos on in, on out, both, or neither — and be able to turn it off where your workplace or local law doesn't fit it. - Keep corrections honest. Missed punches should be fixed through an approval workflow that preserves the original record — not by silently editing the log. ## Where TUKO fits TUKO's attendance clock does exactly this: photo-verified clock-ins (configurable per direction), server-stamped times, private photo evidence with expiring access links, manager-reviewed corrections, and daily summaries that feed timekeeping and payroll directly — in the same app as the rest of your business. ## POS vs ERP: What's the Difference? Small Business Guide URL: https://tukohq.com/learn/pos-vs-erp.html ## What a POS does A point-of-sale system is built around the counter: ring up items, take the payment, print the receipt. Good POS apps are fast, handle cash drawers and card readers, and show daily sales totals. What it deliberately doesn't do: everything upstream and downstream of the sale. Your inventory behind the counter, your supplier balances, your staff's schedules and pay — those live somewhere else. ## What an ERP does An ERP runs the whole business behind the counter as one connected system. Orders, inventory, customers, payments, expenses, HR, and payroll share one database, so a sale isn't just recorded — it updates stock, balances, and reports automatically. ## The practical difference - POS alone: you sell, then separately update stock, separately track who owes you, separately run payroll. - ERP / all-in-one: the sale is the entry point and everything follows from it. If your business is only counter sales with cash — a POS may genuinely be enough. The moment you take orders by chat or phone, sell on credit, track consignment stock, or employ staff, the counter tool leaves you reconciling the rest by hand. ## The modern answer: both, merged The newer all-in-one apps blur the line — the POS is just one screen of the same records. TUKO takes that approach: orders update inventory and receivables the moment they happen, and the same app runs attendance and payroll for the team behind the counter. ## How to Manage Employee Schedules & Leave in One App URL: https://tukohq.com/learn/schedules-and-leave-one-app.html ## Why they belong together Schedules, leave, and attendance look like three different problems — but they're all versions of who worked, when: - The schedule is the plan — who should work, and when. - Attendance is the record — who actually did. - Leave is the explanation for the gap between them. Keep them in separate tools and you reconcile them by hand every pay period — the exact chore that makes small-business payroll error-prone. ## What a unified flow looks like - Set shift patterns once. Generate the roster; override individual days when needed. - Employees clock in from their phone. The app records the timestamp; corrections go through review, not edits. - Leave is a workflow, not a chat. Each request has a status — pending, approved, rejected — and updates the employee's balance automatically. - Payroll reads the record. Approved attendance becomes pay lines — worked hours, overtime, absences — with no re-encoding. ## The hidden win: auditability When a leave request was approved by a person, at a time, with a balance change attached — disputes end. Employees see the same records you do, so the answer to "how many leave days do I have left?" is a lookup, not a negotiation. ## Where TUKO fits TUKO runs this flow end to end: schedules, clock-ins, and leave feed payroll directly — and sit alongside orders and inventory in the same app, so the whole business shares one system. ## How to See Your Whole Business at a Glance URL: https://tukohq.com/learn/see-whole-business-at-a-glance.html ## The check-in call is a habit, not a system You step out for a supplier meeting, a pickup, a rare afternoon off — and the first thing you do is message the store. Is it busy? Did the delivery land? Who came in? The answers come back as "okay naman" and a photo of the counter. You're not reading the business; you're reading confidence levels. Reports don't fix it either. Yesterday's sales summary is accurate and useless for right now. The question an owner actually asks is live: what is happening across my business at this moment? ## What "at a glance" has to answer - Is it busy? Not a chart to interpret — a shape. Is today's activity tall or flat, and compared to what? - Is anything wrong? The low stock, the overdue invoice, the district that's quietly underperforming — surfaced, not buried in tab four. - Who's there? Who punched in, which register is open — presence, not a schedule you hope got followed. - What moved? The transfer that left the warehouse this morning — did it land where it was headed? A dashboard can answer some of these if you already know where to look. The point of a map is that you don't have to know where to look. ## A map beats a dashboard when you don't know where to look Dashboards answer the questions you thought to ask. TUKO Business World draws the whole business as a landscape: fourteen districts — money, sales, stock, cash, customers, POS, people, locations — rise as towers. Height is activity, color is health, a beacon means a Business Pulse signal is waiting. A wrong thing is visually loud before it's a problem you're told about. Beside the towers sits the live campus: every real location — HQ, branch, kiosk, warehouse — stands as its own building sized by how busy it is right now. Staff who punched in appear inside their site, cashiers with open registers stand out, completed stock transfers arc between sites, and each new order or punch pulses where it happened. Selecting a staffed site lets you step inside it. ## It only works because it's your real data The world isn't a demo layer with pretty mock numbers — it's the same organization-scoped records your reports read, under the same permissions and row-level security. Districts you can't access render dimmed. A site with no records shows as quiet — it doesn't pretend to be zero sales. When employee visibility is restricted, names become role labels and counts report as unknown instead of inventing a number. That's the difference between a status board and a map: a status board summarizes what someone decided to report. The map draws what the records already say — so the answer to "how's the shop" is finally yours, not relayed. Open it from More → Business World on any device. No WebGL or a screen reader? The same districts, sites, people, and activity list as plain accessible content. Try TUKO free — questions to support@tukohq.com. ## When Should a Small Business Stop Using Spreadsheets? URL: https://tukohq.com/learn/stop-using-spreadsheets.html ## Spreadsheets are great — until they're your system A spreadsheet is the best analysis tool ever made and one of the worst databases. The problem isn't Excel — it's asking a document to be your business's system of record. These are the signs that line's been crossed. ## 1 — More than one person touches the numbers The moment two people maintain the sheet, you get copies: inventory_FINAL_v3_real.xlsx. Whose version is right? A system of record has exactly one version — everyone sees the same live numbers, with roles deciding who can change what. ## 2 — Your stock count is always behind your sales If you update inventory after selling, the number is always wrong. Customers get promised stock you don't have; you reorder things you didn't need. In a connected system, an order deducts stock the moment it's placed — the count is never stale. ## 3 — Payroll is rebuilt by hand every period Copying attendance into a payroll formula every cutoff is where errors get expensive — one broken cell, one wrong payday. Attendance should feed the pay run directly: worked days, overtime, and leave becoming pay lines automatically. ## 4 — Balances live in someone's memory "Mrs. Santos still owes us… about five thousand?" If customer credit is tracked in notebooks, chat threads, or your head, you're lending money without a ledger. Balances should compute themselves from real orders and payments — with aging that shows how overdue each amount is. ## 5 — You check five tabs to decide what to do today Morning ritual: open the sales sheet, the stock sheet, the receivables sheet, the schedule, the payroll tab — then decide. A connected system reads the same data and tells you the three things that matter today. ## What graduating looks like You don't migrate a business — you switch its system of record. Import customers, products, and opening balances by CSV. From that day, orders update stock, clock-ins feed payroll, and balances compute themselves. Keep using spreadsheets for what they're great at — one-off analysis — and export CSVs whenever you need them. That's what TUKO is built for: see the full comparison, or try it free. ## How to Track Inventory and Orders in One App URL: https://tukohq.com/learn/track-inventory-and-orders.html ## The three-copies problem Most small product businesses run the same sale through three systems: the order book (or chat thread), the inventory sheet, and the money spreadsheet. Each is reasonable alone. The problem is that the three copies are maintained by hand — and drift apart. You see the symptoms: stock says 12 but the shelf says 7. An order is marked paid in the book but the receivables list still shows it open. The count is only trustworthy the day after a physical audit. ## What "one app" actually does When inventory and orders share one system, a sale stops being three tasks: - Stock decrements itself. Confirm an order and inventory levels drop automatically — nothing to copy across. - Overselling stops. The app knows what's on hand before you promise it, not after. - Balances stay true. The order's payment status and the customer's balance are the same record, not two lists to reconcile. - Reports appear for free. "What's selling" and "who owes me" are queries, not Saturday work. ## How to set it up (a practical order) - Import your products — names, prices, current stock. A CSV or an evening of entry is fine; you only do it once. - Add your regular customers — especially anyone who buys on credit. - Record the next order in the app, not the notebook. Don't backfill history — start forward. - Close the loop: record payments against orders so receivables stay real. Within a week the app — not the spreadsheet — is the source of truth, and the sheet becomes a read-only archive. ## Where TUKO fits TUKO is built for exactly this: inventory, orders, customers, and payments in one app — plus expenses, reports, and payroll when you need them. Free to start; works on web and mobile. ## What Is an ERP? A Small Business Guide URL: https://tukohq.com/learn/what-is-erp.html ## ERP, minus the jargon Enterprise resource planning is a terrible name for a simple idea: one system that runs your company's core operations. Orders, inventory, purchasing, customers, money in and out, employees, and payroll — connected so that doing the work updates the records. The opposite of an ERP is what most small businesses actually run: a point-of-sale here, an inventory sheet there, payroll in another spreadsheet, balances in someone's memory. Each tool is fine alone; the tax is re-entering the same truth four times — and the four copies slowly disagreeing. ## Why "ERP" got a scary reputation ERP earned its enterprise reputation honestly: the first generation (SAP, Oracle, and friends) required consultants, months of implementation, and six-figure budgets. Small businesses reasonably concluded it wasn't for them. Two things changed. The cloud removed the servers and IT staff. And a new generation — including simpler modular ERPs and all-in-one apps like TUKO — removed the implementation project. The category's promise stayed the same; the price of admission collapsed. ## Signs you're ready for one - You re-enter the same data in more than one tool - Your stock count is only accurate right after a manual count - Customer or supplier balances live in memory, not a ledger - Payroll means rebuilding formulas and re-encoding attendance each period - You can't answer "who owes me what" or "what's selling" in under a minute Three or more? You've outgrown the spreadsheet stack — see the five signs in detail. ## ERP vs. accounting software vs. a stack of apps Accounting software records what already happened financially. An ERP runs the operations that produce those numbers — so the financials are a byproduct, not a separate chore. A stack of single-purpose apps (inventory app + invoicing app + HR app + payroll app) recreates the same problem with better UI: integrations to maintain, data in five places, five subscriptions. An all-in-one app like TUKO sits in the middle: ERP coverage — orders, inventory, payments, attendance, payroll — sized for a small business, working the day you sign up. ## POS Software for Windows: Buyer's Guide for Small Shops URL: https://tukohq.com/learn/windows-pos-software.html ## Installed app vs browser tab Most "POS for Windows" is really a website — your POS living in a Chrome tab. It works until it doesn't: the tab can't own storage on the PC, can't talk to your receipt printer directly, can't stay signed in securely across restarts, and can't do anything when the internet drops mid-sale. An installed Windows app is a different class of thing. It owns durable storage on the machine, so it can queue sales with no internet. It holds your session encrypted by Windows itself. It prints straight to the printer you picked — no dialog per sale. And it can lock a shared PC to one screen, which is what a counter kiosk actually needs. ## The checklist that matters - Real offline mode. Not "view your catalog offline" — take sales, queue them durably on the PC, and replay them on reconnect without double-posting. See how a real offline POS works. - Direct receipt printing. Pick the printer once; every receipt after that prints silently. A print dialog per sale slows the counter to a crawl. - Self-updating. Tills are the worst place to do manual updates — the app should check and update itself between sessions. - Secure session storage. Your sign-in should live in Windows' own encrypted storage (DPAPI), not a plaintext file any user of the PC can read. - Part of your records, not beside them. A POS that only does the cart leaves you re-entering sales into inventory, books, and payroll. The register should write to the same system that runs the rest of the business. - Modest hardware needs. It should run well on the PC you already have — a lightweight app, not a machine upgrade in disguise. ## What the hardware side looks like The good news: almost nothing. Any Windows 10 or 11 PC made in the last several years runs a modern POS comfortably — a dual-core CPU, 4 GB of RAM, half a gigabyte of disk, and a 1024×640 screen is the floor. A thermal receipt printer on USB or the network and a webcam (for a photo-verified clock-in kiosk) are the only optional extras. Full specs are on the TUKO for Windows page. ## Where TUKO fits TUKO for Windows is built to exactly this checklist: an installed desktop app whose register and attendance kiosk keep working offline, receipts that print straight to a chosen printer, sessions sealed by Windows' own encryption, automatic updates, and the same workspace as the web and mobile apps — one account, one set of records, no side system to reconcile. ## TUKO Storefront — Your Own Online Store, Connected to Your Business URL: https://tukohq.com/storefront/ ## What it is TUKO Storefront publishes a branded online store from the catalog a merchant already keeps in their TUKO workspace. The store gets its own address on the TUKO storefront host. Customers browse published products, add to a persistent cart, and check out for delivery or pickup — and every order lands in TUKO as a canonical sales order tagged to the online channel. ## Why it is different from a standalone store builder A standalone shop builder hands you a second business: a second product catalog, a second inventory count, a second customer list, and a second order queue that must be reconciled into whatever runs the rest. A TUKO storefront is the same business with a public front door — products, stock, customers, orders, payments, and Business Pulse signals all stay in one system. Merchants who already sell on Shopify, WooCommerce, Wix, or Squarespace can keep those stores synced through TUKO integrations alongside their own storefront. ## What a merchant configures Setup happens in the TUKO app's Storefront section: a wizard for store name, address slug, tagline, and template; color presets, accent color, and header style; logo and contact details; SEO title and description; per-product visibility and featured toggles drawn from the existing catalog; custom about, FAQ, policy, and free-form pages; delivery with optional fee and lead-time note plus pickup at chosen locations; and payment methods. Publishing snapshots the whole configuration into a versioned release with rollback and a readiness checklist; drafts never touch the live store. ## How customers pay Merchants choose per store: cash on delivery, bank transfer, and e-wallet transfer with their own written payment instructions — or online card, GCash, and Maya through PayMongo hosted checkout under the merchant's own credentials. PayMongo remains unavailable until an admin connects credentials, which are stored encrypted server-side and never reach the browser. A browser redirect is never treated as proof of payment; only the provider's verified webhook marks an order paid, and payment attempts are recorded for review. ## Trust and safety details Checkout prices and stock are validated server-side against the published catalog — the browser sends product and quantity only. Guests track orders with an order number and email; no customer accounts exist. Storefront checkouts are rate-limited and idempotent so retries cannot duplicate orders. Contact forms carry honeypot and rate-limit protections, and inquiries land in a permission-gated triage inbox inside the TUKO app. ## Discoverability Every published storefront serves its own sitemap.xml, robots.txt, canonical and Open Graph/Twitter tags, JSON-LD Product markup on product pages, and an llms.txt describing the business and catalog for AI answer engines. ## Cost Storefront is part of free TUKO Core — no subscription, no per-product, per-order, or per-visitor fee from TUKO. PayMongo's own processing fees apply only when a merchant enables online payments through their own PayMongo account. Custom domain support is on the roadmap.