Demosite — Full Scope & Requirements Register

The home page automatically builds a to-do list from what's happening across your business — items out of stock or running low, approvals waiting on you, open customer conversations, and unfinished orders, broadcasts, campaigns, or content. Each item links straight to where you can act on it.

• You can check this by confirming items that are completely out of stock, or down to 5 units or fewer, take you to the Inventory page when clicked
• You can check this by confirming approvals waiting on you, open customer conversations, and unfinished orders each show up as one line with a live count
• You can check this by confirming customers who haven't ordered in 45 days link straight to their customer page

The to-do list is sorted so the most urgent problems appear first, no single type of issue can flood the list, and only the 8 most important items show at once.

• You can check this by confirming urgent issues always appear above warnings, which appear above opportunities
• You can check this by confirming the list never shows more than 8 items, with the very first one visually highlighted
• You can check this by confirming no single category (like low stock or draft broadcasts) can take over more than 2 slots on the list (drafts are capped at 1)

The home page shows four quick numbers: how many products you carry, how many units you have in stock, how many orders you've had, and how many customers you have.

• You can check this by confirming all four number tiles appear below the to-do list
• You can check this by confirming the numbers update correctly when switching between 'all locations' and a single location

When there's nothing that needs your attention, the page shows a friendly 'all caught up' message with a checkmark instead of leaving the screen looking empty or broken.

• You can check this by clearing every action item and confirming the checkmark message appears
• You can check this by confirming the 'start here' hint only shows when there are actual items to work through

Each staff member only sees to-do items for the business location(s) they're responsible for. The page is also built to be easy to tap on a phone and works fully in both English and Chinese.

• You can check this by confirming a staff member assigned to one location never sees another location's items, while a head-office user viewing 'all locations' does see items across locations
• You can check this by confirming every item on the list is large enough to comfortably tap on a phone screen
• You can check this by confirming every piece of text on the page is available in both English and Chinese

You can view performance for today, yesterday, this week, this month, this quarter, this year, all time, or any custom date range you choose. Your last choice is remembered the next time you visit.

• You can check this by picking a quick option like 'this month' and confirming the numbers update instantly
• You can check this by entering a custom range with the end date before the start date and confirming it falls back to showing all-time data rather than guessing
• You can check this by refreshing the page and confirming your last-picked time period is still selected

The dashboard can compare the current period to the previous period or to the same period last year, showing whether each number went up or down. If there's nothing to compare against, it honestly shows a dash instead of a misleading percentage.

• You can check this by selecting a quarter and confirming it compares against the correct prior quarter, including across year boundaries
• You can check this by picking a period with zero prior sales and confirming it shows a dash, not a fake percentage
• You can check this by confirming the margin and target tiles never display a comparison arrow

The dashboard displays six core numbers for the selected period: total sales, units sold, number of orders, average order value, profit margin percentage, and how close you are to your sales target.

• You can check this by confirming all six tiles show a value for whatever period you've selected
• You can check this by confirming the sales and units tiles include a small trend line

The dashboard shows a long-term monthly sales trend for each location, a breakdown of where sales come from (retail store, website, social platforms, etc.), and your 5 best-selling and 5 slowest-selling products.

• You can check this by confirming the monthly trend chart always shows the full history, regardless of which time period is selected elsewhere on the page
• You can check this by confirming the sales-channel chart only shows real recorded sales, never made-up numbers
• You can check this by confirming products with zero sales still appear in the slow-movers list, since that's useful to know

The dashboard shows each location's sales target against actual sales, color-coded green when you've hit the target, yellow when you're close, and red when you're falling short.

• You can check this by confirming a head-office user sees one row per location, while a location-level user only sees their own location, in their own local currency
• You can check this by confirming the monthly targets are Malaysia RM500,000, China ¥150,000, and International $20,000

Head-office users can switch the whole dashboard between US dollars, Malaysian ringgit, Chinese yuan, or Singapore dollars. Each past sale is converted using the exchange rate from the date it actually happened, not today's rate, so historical numbers stay accurate.

• You can check this by switching currencies and confirming every figure on the dashboard updates
• You can check this by confirming a sale from months ago converts using the exchange rate from that date, not today's

Every revenue figure on the dashboard is calculated the same consistent way: only orders that have been paid or fulfilled count as revenue. Draft, cancelled, and refunded orders never inflate the numbers.

• You can check this by confirming only paid and fulfilled orders are counted in any revenue figure
• You can check this by confirming a draft, cancelled, or refunded order never adds to revenue anywhere on the dashboard

All money calculations are done in whole cents internally so there's never a rounding error, and every section of the dashboard shows a loading animation while data loads and a clear message when there's no data to show.

• You can check this by confirming money figures never show rounding artifacts
• You can check this by picking a period with zero orders and confirming the charts show a clear 'no data' message instead of appearing broken or blank

Managers can set a monthly goal for a team member — a sales target, a units-sold target, or a custom goal — and optionally attach a bonus multiplier between 100% and 200% of the standard bonus.

• You can check this by confirming non-manager staff see a read-only view instead of the option to create or evaluate goals
• You can check this by confirming the team member, a label, and the month are always required when creating a goal

A goal starts active and can only end as achieved, missed, or cancelled — once it reaches one of those, it's locked and can't be changed again.

• You can check this by confirming the status options disappear once a goal reaches achieved, missed, or cancelled
• You can check this by confirming the system rejects any attempt to move a goal to an invalid stage

Managers can recalculate whether each active goal was hit, based on that month's actual sales, and the system automatically marks it achieved or missed. Running the check again doesn't create duplicate records or change anything if nothing new has happened.

• You can check this by confirming a sales-target goal is marked achieved only once actual sales reach the target amount
• You can check this by running the evaluation twice in a row with no new sales and confirming nothing changes the second time

Tasks move through a fixed set of stages — to do, in progress, blocked, and done — and the person a task is assigned to can update its status themselves, even without manager permissions. Overdue tasks are flagged automatically.

• You can check this by confirming the board always shows 4 columns with a live count of tasks in each
• You can check this by confirming the assigned person can move their own task without needing manager access
• You can check this by confirming a task past its due date and not yet done is visibly flagged as overdue

The page shows the 10 most recent goal and task changes for whatever team or location you're viewing, newest first.

• You can check this by confirming the activity list never shows more than 10 rows
• You can check this by confirming you only see activity for your own location unless you have company-wide access

Staff can only see goals and tasks for their own location, unless they have company-wide access. Any change they make is automatically tied to their own workspace, so it can't accidentally affect another location.

• You can check this by confirming finance and support staff never see options to create or change goals/tasks, regardless of what they can view
• You can check this by confirming every change made is automatically recorded against the correct location and person

The inventory page shows every product with its stock and price together, in your choice of three layouts (large cards, medium cards, or a list), with filters for text, category, color, size, and stock status.

• You can check this by switching layouts and confirming your choice is remembered next time you visit
• You can check this by confirming the page tells you clearly whether there are simply no products yet, or your filters just don't match anything
• You can check this by confirming a product with different prices across its variants shows a price range rather than one misleading number

Each product can be expanded into a grid showing stock for every color and size combination, with red highlighting sold-out items and yellow highlighting low stock (5 units or fewer).

• You can check this by confirming any combination with 5 or fewer units is highlighted yellow, and 0 units is highlighted red
• You can check this by confirming a color/size combination the product doesn't even offer shows a dash, not a misleading zero
• You can check this by confirming sizes always appear in standard order from smallest to largest

Admins can create a brand-new product and generate every color and size combination it comes in, with starting stock levels for each, all in a single submission. The system shows a live preview of how many variants will be created and won't allow two products with the same product code.

• You can check this by creating a product with 3 colors and 4 sizes and confirming 12 variants are created in one go
• You can check this by confirming trying to reuse an existing product code within the same company is rejected

Clicking a stock cell gives managers a full edit form for stock and price, gives support staff a simpler +/- adjustment tool that won't let stock go negative, and shows finance staff a read-only view.

• You can check this by confirming finance staff can never edit a stock cell
• You can check this by confirming support staff can't submit an adjustment that would push stock below zero

Staff can update stock or prices for many items at once. Stock changes apply immediately, but price changes must be requested by a manager and approved by a different person (a manager or finance) before they take effect — no one can approve their own price request.

• You can check this by confirming a bulk stock change applies right away, while a bulk price change goes into an approval queue first
• You can check this by confirming the person who requested a price change cannot also approve it
• You can check this by confirming an approved price change applies correctly, and any item that was deleted in the meantime is reported as skipped rather than silently ignored

The system checks in three different places that stock can never drop below zero, so even if one check were somehow bypassed, the others would still catch it.

• You can check this by attempting to remove more stock than is available through any of the editing tools and confirming it's always blocked
• You can check this by confirming this holds true no matter which of the three editing paths (form, adjustment panel, or bulk edit) is used

The product catalogue (names, colors, sizes) is shared across all your locations, but each location has its own separate stock and pricing. Every change requires the right permissions for that specific location.

• You can check this by confirming finance staff can view but never edit anything on this page
• You can check this by confirming a head-office user viewing 'all locations' can see everything but still can't edit a location they don't manage

You can upload a spreadsheet (CSV file, up to 5MB) of products, stock, customers, or orders, match its columns to the right fields, preview exactly what will change, and only then confirm the import. Nothing is saved until you approve the final step.

• You can check this by confirming a file that isn't a CSV, or is over 5MB, is rejected upfront
• You can check this by re-running an already-completed import and confirming it tells you it was already done instead of importing everything twice
• You can check this by starting an import, leaving the page, and confirming your progress is saved when you return

Each type of import checks for the required information (for example, products need a product code and name; customers need a name and a valid email) and flags any row that's missing something, so you can fix it before importing. Column headers in English, Chinese, or from common sales platforms are recognized automatically.

• You can check this by uploading a row missing a required field and confirming it's flagged with a clear reason
• You can check this by uploading a spreadsheet with Chinese column headers and confirming they're matched automatically

The import process automatically detects duplicate rows within the same file and checks against existing records, so you always see clearly which rows are brand new, which are updates to existing records, and which are exact duplicates that will be skipped.

• You can check this by including the same row twice in one file and confirming only the first copy is kept
• You can check this by re-importing a record with no changes and confirming it's marked as a duplicate, not imported again
• You can check this by running a preview and confirming it never actually saves anything until you commit

The system includes a demo connection that simulates pulling in orders and products from an online store, with a preview mode and a choice of how to route the incoming data across your locations. This is a demonstration only — no real store is contacted.

• You can check this by confirming no live internet connection to a real store is ever made
• You can check this by running the sync twice and confirming the second run correctly identifies already-imported records as duplicates

Staff can manually create a single new product code with its stock, or adjust an existing item's stock up or down with an optional note explaining why. Every manual change is recorded in the history.

• You can check this by confirming a new product code requires at minimum a code, name, and variant label
• You can check this by confirming a stock adjustment requires an actual non-zero amount, and the reason you enter is saved with it

A read-only list shows every past import for your current location, so you can see what was imported and when.

• You can check this by confirming the history only shows imports for the location you're currently viewing

Only the right roles can import or adjust data, and this is checked both on the screen and again behind the scenes, so it can't be bypassed. Finance staff can only view, never import.

• You can check this by confirming finance staff see a locked, disabled import screen
• You can check this by confirming every import is tied to the correct location and can't accidentally affect another one

The sales list shows every order with the date and time, customer, which staff member made the sale (or a clear 'self-serve' label if no one did), which of the 7 sales channels it came through, how many items, the total, and its current status.

• You can check this by confirming self-serve orders always show a clear label instead of a blank space
• You can check this by confirming all 7 channels — retail store, website, TikTok Shop, Shopee, Lazada, Instagram, and WhatsApp — display with their own distinct badge

You can search orders by order number or customer name as you type, and filter by sales channel, salesperson, status, or date range, with a running count of matching results.

• You can check this by confirming there's a specific filter option for orders with no salesperson attached
• You can check this by confirming the page tells you clearly whether there are simply no orders yet, or your filters just don't match anything

Clicking any order opens the same detailed view whether it opens as a side panel or its own full page — order summary, items, status history, and activity log are identical either way.

• You can check this by opening the same order both ways and confirming they show identical information
• You can check this by looking up an order that doesn't exist and confirming it shows a clear 'not found' message

Before an order is created, the system checks that every item on it is actually in stock. Once confirmed, stock is reduced and the order is recorded as one single, safe step, then the customer and staff are notified.

• You can check this by attempting to order more of an item than is in stock and confirming it's blocked with a clear message before anything is saved
• You can check this by confirming finance staff don't see the option to create a new order

An order can only move from draft to paid or cancelled, then from paid to fulfilled or refunded, and from fulfilled to refunded. Cancelling or refunding an order automatically puts the stock back, and every single stage change is recorded in the history.

• You can check this by confirming an invalid stage change (like going straight from draft to fulfilled) is blocked
• You can check this by cancelling or refunding an order and confirming the stock is restored as part of that same action, not a separate step that could be missed

No refund happens automatically. A manager requests it, and it only goes through once a different manager or finance staff member approves it. While it's waiting, the order clearly shows 'refund pending.'

• You can check this by confirming there is no way to refund an order without going through the approval request
• You can check this by confirming the person who requested the refund cannot also be the one who approves it

If a customer who had gone quiet places a new order, the system automatically marks them as active again — this is the only status change in the whole system that happens automatically, and it's fully recorded.

• You can check this by confirming the customer's activity history shows the reason as 'won back by order' with the order number
• You can check this by confirming this doesn't trigger a duplicate or unnecessary notification

Every change to an order and its history entry are saved together as one action — if anything goes wrong partway through, nothing is saved at all, so the records can never end up out of sync. Money is always calculated in exact cents, never rounded incorrectly.

• You can check this by confirming that if the history entry can't be written, the order change itself is also cancelled, not left half-done
• You can check this by confirming order totals never show rounding errors

Managers can set commission rules as a percentage of sales, a flat amount per order, or a flat amount per unit sold — for the whole team or one specific person — with an optional start and end date. A rule for a specific person always takes priority over a general team rule.

• You can check this by confirming a rule set for one specific salesperson overrides the general team rule for that person
• You can check this by confirming the commission rate must be a positive number, and creating a rule is recorded in the history

Managers can calculate commissions for the month with one click. Running it again doesn't create duplicate payouts for the same order and salesperson, and anyone with no applicable rule or a zero payout is simply skipped.

• You can check this by clicking calculate twice in a row and confirming no duplicate entries are created
• You can check this by confirming a percentage-based commission always rounds down, in the business's favor

Each commission payout starts as pending, can be approved or disputed, and only an approved payout can be marked as paid. Only a manager or finance can approve or pay, and the salesperson is notified at each step.

• You can check this by confirming an invalid change (like marking a pending entry as paid without approving it first) is blocked
• You can check this by confirming the salesperson gets a notification once their commission is approved and again once it's paid

The page shows each salesperson's total commission for the selected month, with a status badge showing their most urgent item (a disputed entry always takes priority for visibility), and lets you drill into the details.

• You can check this by confirming a salesperson with even one disputed entry shows a disputed badge, not a paid one
• You can check this by confirming the recent activity log shows up to 8 recent commission changes

Only managers can create commission rules and run calculations. Only managers or finance can approve and pay out commissions. Everyone else can only view, and always only for their own location unless they have company-wide access.

• You can check this by confirming support staff can view but never create rules or approve payouts on this page
• You can check this by confirming the same role rules apply consistently everywhere this page is used

Creating a payroll run generates a payslip for every team member at that location, combining their base salary with their approved commission for the month. Once created, a payslip is locked in — it won't change even if commission figures change later. You can't accidentally create two payroll runs for the same location and month.

• You can check this by confirming a payslip's numbers stay the same even if commission amounts are later recalculated
• You can check this by trying to create a second payroll run for a location/month that already has one and confirming it's blocked with a reference to the existing run

A payroll run moves from draft to pending approval, then to approved, then to paid (or can be voided at most stages). Whoever created the run can never approve their own run — this is enforced by the system itself, not just hidden in the interface.

• You can check this by confirming the person who created a payroll run sees the Approve button disabled with a clear explanation
• You can check this by confirming the system itself rejects an approval attempt by the run's creator, even if the button were somehow bypassed

Clicking a payroll run opens a panel showing the run's details, only the actions you're allowed to take next, an optional field to note why you're taking an action, the full payslip table with a total, and the run's recent history.

• You can check this by confirming you only ever see buttons for actions you're actually allowed to take
• You can check this by confirming the activity history shown is specific to that payroll run

The moment a payroll run is marked as paid, every team member at that location gets an in-app notification. If a notification fails to send for any reason, it never blocks or delays the payment itself.

• You can check this by confirming all team members at the location receive a notification once a run is marked paid
• You can check this by confirming a failed notification never prevents the payroll run from completing

If the commission figures can't be retrieved for some reason when creating a payroll run, the system doesn't fail — it simply uses zero for that portion rather than blocking payroll entirely. All money on payslips is calculated in exact cents.

• You can check this by confirming payroll can still be created even if the commission calculation temporarily fails
• You can check this by confirming all payslip amounts are exact, with no rounding errors

You can search customers by name or email, filter by their relationship stage, and see each customer's order count, total spend (always in their own location's currency), and last order date at a glance.

• You can check this by confirming a customer's total spend always shows in their own location's currency, never mixed with another currency
• You can check this by looking up a customer outside your access and confirming a clear 'not found' message appears instead of an error

Adding a customer requires a name and valid email. If that email already exists at the same location, it's blocked as a duplicate. If it exists at a different location, you get a gentle heads-up — but it's never automatically merged and never blocks you from adding them.

• You can check this by trying to add a customer with an email already used at the same location and confirming it's blocked
• You can check this by adding a customer whose email exists at a different location and confirming you see a soft warning, not a block

Every customer is at one of five relationship stages — new, active, VIP, at risk, or dormant — and can only move between the stages that make sense (for example, a dormant customer can only come back to active). Every change is checked by the system itself, recorded, and the customer is notified unless it's meant to be silent.

• You can check this by confirming staff only ever see valid next-stage options as buttons
• You can check this by confirming a dormant customer's only way back is to active — there's no dead end and no invalid jump

The system watches customer activity and suggests a status change when the data suggests one is due — for example, suggesting 'at risk' after 45 days of no orders. These are only suggestions; staff always have to apply them manually.

• You can check this by confirming a suggestion appears only when the customer's actual status doesn't match what the data suggests
• You can check this by confirming no suggestion is ever applied automatically without a staff member clicking to accept it

Staff can log 4 types of customer outreach — a suggestion, a reminder, a newsletter, or a gift — with an optional note. Each one notifies the customer and is saved to their history alongside their status changes, newest first.

• You can check this by confirming all 4 touchpoint types are available no matter what stage the customer is at
• You can check this by confirming the customer's history shows the note, who logged it, and when

Staff who aren't allowed to make changes to a customer's record don't just see those options grayed out — they don't see them at all. Finance staff can only view.

• You can check this by confirming a read-only staff member sees no edit buttons whatsoever, not even disabled ones
• You can check this by confirming any change requires both the correct location and the correct role

All customer messages and system alerts show up together in one list, newest first, so staff never have to check multiple places. Unread items are clearly marked, and staff can filter to see everything, just open items, or just resolved items.

• You can check this by opening the inbox and seeing customer messages and system alerts mixed into a single, newest-first list
• You can check this by confirming unread items are clearly marked, and that clicking one marks it read and opens the full conversation
• You can check this by switching between All, Open, and Resolved filters and seeing the list update correctly

Staff can start a new message thread, optionally linking it to a specific customer, and choose whether to notify that customer in-app, by email, or both.

• You can check this by starting a new conversation with a subject and message, optionally attaching it to a customer record
• You can check this by confirming the new-conversation screen slides up from the bottom on mobile and opens as a pop-up on desktop
• You can check this by linking a customer, checking a notification method, and confirming that customer receives the message through it

Staff can reply to any open conversation, and managers can mark a conversation resolved once it's handled. A resolved conversation can't be replied to or resolved again.

• You can check this by replying to an open conversation and confirming the linked customer is notified
• You can check this by confirming only managers, not regular support staff, can mark a conversation resolved
• You can check this by trying to resolve the same conversation twice — the second attempt is blocked

The inbox list stays a manageable size on screen and shows a friendly message when there's nothing to show. If a conversation can't be found, staff still see something useful instead of an error.

• You can check this by scrolling a long inbox list and confirming it stays contained rather than making the whole page grow endlessly
• You can check this by confirming an empty inbox shows a clear 'nothing here' message instead of a blank space

Staff write a message, choose who receives it (all customers, only customers who've ordered, or only those who haven't), and pick how to send it (in-app, email, or both), with a preview of who will actually receive it before sending.

• You can check this by trying to move to the next step without filling in the subject and message — it's blocked
• You can check this by selecting an audience group and at least one delivery method, then confirming the preview shows a real, live list of recipients

Who actually receives the message is worked out at the moment of sending, not when it was written, so the list stays accurate even if customers changed in between. If delivery fails for one customer, it doesn't stop the message going to everyone else.

• You can check this by confirming the final recipient count matches who qualified right at send time, not at compose time
• You can check this by confirming a delivery failure for one customer doesn't block delivery to the rest of the batch

A draft message can either be sent or cancelled. Once it's been sent, it can't be cancelled or edited.

• You can check this by confirming a sent broadcast no longer shows a cancel option
• You can check this by confirming send and cancel buttons only appear for draft messages, and only for staff with permission

Staff can see how many customers were targeted versus how many actually received the message, broken down by delivery method, plus a log of sent messages and a recent activity history.

• You can check this by comparing the 'targeted' and 'delivered' numbers shown for a sent broadcast
• You can check this by confirming the send log only appears once at least one broadcast has actually been sent

Only managers and entity managers can create, send, or cancel broadcast messages. Finance staff and support staff can view them but not send.

• You can check this by logging in as finance or support staff and confirming you only see a 'view only' notice, with no send or cancel buttons

Managers can create a discount campaign with a name, a promo code (automatically capitalized and unique within their business), a discount type (percentage off, flat amount off, or buy-one-get-one style), a value, and a start date, with an optional end date.

• You can check this by trying to reuse an existing promo code within the same business — it's rejected
• You can check this by trying to submit the form without a name, code, value, or start date — each one is required

A campaign can be switched from draft or paused to active, and from active back to paused. Every switch is recorded, and turning a campaign on notifies the staff member who did it.

• You can check this by confirming the activate and pause buttons only appear for the right campaign status and staff role
• You can check this by confirming every activate or pause action leaves a record in the activity history

Before a promo code is applied to a sale, the system checks that the code exists, is currently active, is within its valid dates, hasn't hit its usage limit, and that the order meets any minimum spend — then records the discount and counts it against the usage limit.

• You can check this by trying an expired, inactive, or over-limit code — each is rejected with a clear reason
• You can check this by applying a valid percentage-off code and confirming it correctly reduces the recorded discount amount

Each campaign card shows how many times it's been used, the total discount value given out so far, and a list of the individual orders it was used on. A recent activity list shows the latest campaign and broadcast actions.

• You can check this by expanding a campaign card and seeing the list of orders the code was used on
• You can check this by confirming the recent activity list shows at most the 10 most recent actions, newest first

The page shows a card for each of the three connected marketplaces, with its connection status, when it last synced ('Never synced' if it hasn't yet), and how many orders have been brought in so far.

• You can check this by confirming all three marketplace cards always appear, even before a first sync
• You can check this by confirming each card shows a spinner while syncing and a clear success or error message afterward

Running a sync twice in a row never brings in the same order twice — the system remembers which orders it has already seen.

• You can check this by syncing a marketplace, then syncing it again immediately — the second run brings in 0 new orders
• You can check this by confirming the 'last synced' time updates every time, even when no new orders came in

Each new marketplace order is matched to an existing customer and current stock, using the business's own prices rather than the marketplace's, and is recorded immediately as a paid sale. Orders that can't be matched to a customer or any stock are skipped rather than guessed at.

• You can check this by confirming an imported order's price matches the business's own listed price, not whatever the marketplace reported
• You can check this by confirming imported orders show up already marked as paid

Only managers and entity managers can trigger a marketplace sync. Each business location's marketplace data is kept completely separate from every other location.

• You can check this by logging in as a role without permission and confirming the sync button is disabled with an explanation

Staff write content pieces (a title and caption are required, plus a type such as reel, post, carousel, or quote card) and see them listed with live counts by status and a step-by-step progress view.

• You can check this by creating a piece and watching it appear in the list with the correct status
• You can check this by confirming the status filter counts update immediately as pieces move through the pipeline

A content piece moves through fixed stages: draft, rendered, waiting for approval, approved, then either scheduled or published. Support staff can create and prepare content, but only managers can approve and publish it. Every stage change is recorded.

• You can check this by logging in as support staff and confirming there's no way to approve or publish content
• You can check this by trying to skip a stage — it's blocked — and confirming every legitimate stage change appears in the activity history

Before publishing, the system previews how content will look on each platform and automatically trims captions and hashtags and adjusts video length to fit that platform's limits, flagging anything it had to adjust.

• You can check this by entering an overly long caption or too many hashtags and confirming a warning appears showing what was trimmed
• You can check this by confirming a piece that fits all limits shows a 'Clean' badge with no warnings

Publishing sends approved content out to four platforms — YouTube Shorts, Facebook Reels, Instagram Reels, and TikTok — at the same time, and keeps a record for each one. Already-published content can't be published again. Two platforms, Xiaohongshu and WeChat, are deliberately blocked.

• You can check this by publishing a piece and confirming it appears as published on all four platforms
• You can check this by trying to publish the same piece a second time — it's blocked

The tracking page shows key numbers, a breakdown by platform, and a top-5 list, calculated fairly across platforms with different audience sizes. The system deliberately does not invent a single 'virality score,' since that would be misleading.

• You can check this by confirming the watch-through numbers are weighted by how many people actually saw the content, not just averaged
• You can check this by confirming that with no data yet, the page shows a clear empty state instead of an error or blank screen

The assistant tries its best available option first, falls back automatically if that's unavailable, and finally falls back to a built-in assistant that needs no paid subscription at all — so it never simply fails to respond.

• You can check this by using the assistant with no paid subscription set up and confirming it still answers helpfully
• You can check this by confirming that if the paid option fails partway through answering, the assistant recovers and finishes the answer instead of showing an error

The assistant can look things up on its own, but any action that would change data — like issuing a refund — shows a card asking staff to explicitly click 'Run it' or 'Deny' before anything happens. Requesting a refund through the assistant creates an approval request rather than refunding directly, and it won't create a duplicate request if one is already pending.

• You can check this by asking the assistant to change something and confirming nothing happens until you click 'Run it'
• You can check this by asking for a refund twice in a row and confirming only one pending approval request is created

The assistant keeps a history of past conversations, organized by date, which staff can rename, delete, or export. Staff can attach up to 3 files per message (including spreadsheets, PDFs, and Word documents), up to a set size and length limit.

• You can check this by renaming and deleting a saved conversation
• You can check this by trying to attach more than 3 files, or a file over the size limit — it's blocked with a clear message

The built-in fallback assistant understands common questions in both English and simplified Chinese, and gives a helpful, specific response even to questions it doesn't exactly recognize, rather than a generic 'I don't understand.'

• You can check this by asking a specific question, like 'show me order 123,' and confirming it doesn't get confused with a broader question like 'show me all orders'
• You can check this by asking an unrecognized but related question and confirming you get a targeted hint, not a blank shrug

When a paid subscription is connected, the assistant limits how much any one person can use it in a short time, how long its answers can be, how much conversation history it reads, and how many actions it can take in one turn, so costs stay predictable. If someone hits the usage limit, they still get an answer from the built-in fallback instead of being cut off.

• You can check this by exceeding the usage limit and confirming you still get a useful answer, not an error message

The assistant only ever acts using the real permissions of the staff member who is logged in — it can't be talked into pretending someone has a role or access they don't actually have.

• You can check this by confirming permissions are always checked against the real logged-in user, never anything typed into the chat

Managers can submit requests for sensitive actions, covering 8 different types including payroll, commission, staff goals, refunds, and bulk price changes. A separate manager or finance staff member can then approve or reject a pending request, and the original requester or a manager can withdraw it before it's decided. Every step is recorded and the right people are notified.

• You can check this by submitting a request and confirming approvers are notified, then confirming the requester is notified once a decision is made
• You can check this by trying to decide on a request that's already been decided — it's blocked

The person who requested an action can never be the one to approve their own request, even if they try to bypass the normal screen — the system blocks it.

• You can check this by submitting a request and then trying to approve it as the same user — it's blocked with a clear reason

Once approved, refunds and bulk price changes are carried out under the original requester's permissions, so a finance approver without direct edit rights can still approve without the action failing. If carrying out the action fails afterward — for example, a product no longer exists — the approval itself still stands, and the issue is flagged separately rather than undoing the decision.

• You can check this by having a read-only finance approver approve a refund and confirming it goes through
• You can check this by having an item deleted before the approved action runs and confirming it's reported as skipped rather than causing an error

The team page lists staff members — group-level roles see everyone across all locations, others see just their own location — lets managers generate an invitation for a new staff member, and shows a reference table of what each role can do. A location manager cannot grant someone full group-admin access.

• You can check this by generating an invite and confirming it's recorded in the activity history
• You can check this by trying to invite someone as a group admin while logged in as a location manager — that option isn't available

Any user can switch to see the system as any of the 4 demo roles would see it, which makes it easy to demonstrate the request-and-approve process end to end. A full data reset, only available to a top-level admin, requires confirming twice and then reloads with fresh sample data.

• You can check this by switching between the 4 roles from the Team page and seeing the view change accordingly
• You can check this by trying the reset button and confirming it asks for confirmation twice before actually resetting

Every meaningful action in the system is written to a permanent history log that nothing can edit or delete, visible on the Approvals page, the Team page, and each order's own history. If a history entry can't be written, the action itself is cancelled too, so the two always stay in sync. Notifications, on the other hand, are allowed to fail quietly without blocking anything.

• You can check this by confirming there is no button or option anywhere to edit or delete a history entry
• You can check this by confirming every approval, refund, and role change appears in the relevant history log

The platform supports one overall business group with 3 locations: Malaysia (in Ringgit), China (in Yuan), and an international location (in US Dollars). The product catalogue is shared across all locations, but stock, prices, and daily operations are kept separate per location. Senior roles like group admin and finance can view across all locations or switch between them, but any changes they make still apply only to their own home location. Location managers and support staff are locked to their own location only.

• You can check this by confirming a location manager cannot switch to a different location
• You can check this by confirming that viewing 'all locations' as a senior role only widens what you can see, never what you can change

Access rules are enforced twice over — once directly in the software's own logic, and matched by an equivalent set of database-level rules as a second layer of safety. Finance staff can view everything in their scope but never make changes.

• You can check this by confirming every action that changes data double-checks the person's permissions before making the change
• You can check this by confirming finance-role users never see an editable field anywhere in the product

Every piece of text shown to users exists in both English and Chinese, and the system is built so a missing Chinese translation is caught automatically before it ever reaches a customer.

• You can check this by switching the language and confirming every screen is fully translated, with nothing left in the wrong language

Everything staff do is automatically saved to the device's browser storage a fraction of a second after each change, so nothing is lost on reload. If saved data ever becomes unreadable, or is left over from an old, incompatible version, the system safely starts fresh with realistic sample data instead of crashing.

• You can check this by making a change, reloading the page, and confirming the change is still there
• You can check this by confirming that corrupted saved data never crashes the app — it just resets to fresh sample data

The demo works right out of the box with no setup needed. If the business wants to restrict who can view the whole site, turning on one password protects every page and every behind-the-scenes connection, so nobody can access anything — including any connected paid AI features — without that password.

• You can check this by confirming the site is open to everyone when no password is set
• You can check this by turning the password on and confirming every page, not just some, now asks for it

All text sizes and weights across the product come from one central style guide, so the look stays consistent everywhere rather than varying from screen to screen.

• You can check this by confirming headings, labels, and body text look consistent across different pages