[
  {
    "id": "start",
    "group": "start",
    "group_title": "Getting started",
    "title": "Sign in and select a store",
    "paths": [
      "/login",
      "/reset-password",
      "/admin/no-store"
    ],
    "paragraphs": [
      "Sign in with your staff account. Products, orders and store settings follow the selected store, so check its name before making changes."
    ],
    "steps": [
      "Enter your sign-in details and wait for the panel. Read any rejection message before retrying.",
      "Select an available store from the top store switcher. Disabled or unassigned stores cannot be entered.",
      "Use the language button to switch Arabic and English without changing the store.",
      "Use password recovery when needed. A no-store-access screen means an administrator must review your store assignments."
    ],
    "fields": [
      "Current store: determines the data and store permissions in use.",
      "Language: changes panel labels and direction; product translations are entered separately."
    ],
    "tips": [
      "A missing screen or rejected link can indicate a missing screen permission. Viewing and editing are separate permissions.",
      "Products belong to one store. Countries are shared reference data; mobile-app settings apply to all stores of the same client. Their sections explain these exceptions."
    ],
    "examples": [
      "An employee assigned to two stores selects the intended store before finding a product; matching names do not imply shared stock."
    ],
    "troubleshooting": [
      "No store is available: check store activation and assignment before signing in again."
    ]
  },
  {
    "id": "account",
    "group": "start",
    "group_title": "Getting started",
    "title": "Staff account, password and panel appearance",
    "paths": [],
    "paragraphs": [
      "Use the header account menu to change your staff password or sign out, and header controls to change language, appearance or find a screen."
    ],
    "steps": [
      "Open your account menu and choose change password.",
      "Enter current password, new password and matching confirmation, then save and inspect the outcome.",
      "Use appearance controls for light/dark mode and navigation controls to expand the menu or open it on mobile.",
      "Sign out when finished on a shared device and keep staff accounts individual."
    ],
    "fields": [
      "Current password: confirms the account owner before changing credentials.",
      "New password and confirmation: must match and satisfy validation.",
      "Screen search: a navigation shortcut, separate from product or order list search.",
      "Password changes revoke other sessions under the system policy; review the notice and sign in again if requested."
    ],
    "tips": [
      "This changes the current staff account password, not a storefront customer password. Do not change demo credentials merely to test documentation."
    ],
    "examples": [
      "Separate staff accounts make audit history and order-creator sales meaningful."
    ],
    "troubleshooting": [
      "Incorrect current password: correct it or use recovery; language and store switching do not change the password."
    ]
  },
  {
    "id": "access-errors",
    "group": "start",
    "group_title": "Getting started",
    "title": "Access denied and page not found",
    "paths": [
      "/admin/unauthorized",
      "/404"
    ],
    "paragraphs": [
      "Access denial can indicate missing screen permission. Page not found can indicate an invalid or outdated route."
    ],
    "steps": [
      "Check the page address and selected store.",
      "Return to the sidebar and use its current screen link rather than guessing record addresses.",
      "For continued denial, review store assignment and screen permission; for missing records, inspect filters, deletion and access."
    ],
    "fields": [
      "Access denied: the account is not authorized for the requested context.",
      "Not found: no matching page; this alone does not prove store records were deleted."
    ],
    "tips": [
      "Grant only required screen and action access rather than broad financial or administrative permissions."
    ],
    "examples": [
      "A user with order viewing but no editing can open an order without modification actions."
    ],
    "troubleshooting": [
      "A link is denied after switching stores: check the account’s assignment and permissions in the new store."
    ]
  },
  {
    "id": "guide",
    "group": "start",
    "group_title": "Getting started",
    "title": "User guide and assistant",
    "paths": [
      "/admin/guide"
    ],
    "paragraphs": [
      "This reference follows the sidebar groups. Each screen explains its purpose, operating steps, fields and expected outcomes."
    ],
    "steps": [
      "Choose a contents group or search for a screen, action or field.",
      "Expand a screen and follow its steps, then review its notes before saving.",
      "Expand all matching explanations or print them using the browser print dialog.",
      "Open the top-bar assistant for usage questions; it uses this same guide.",
      "Use practical examples to understand a concrete case, then check Common problems and solutions when the outcome differs."
    ],
    "fields": [
      "Search: includes titles, descriptions, steps, fields and notes.",
      "Group: limits the reference to one area; select all groups to restore the complete guide.",
      "Search also includes examples, troubleshooting, section identifiers and screen paths; try POS, abandoned carts or a route name."
    ],
    "tips": [
      "The assistant cannot inspect live orders or change prices and settings. Its server configuration may be required.",
      "Printing includes the current results. Clear search and choose all groups to print the whole guide."
    ],
    "examples": [
      "Search half an hour for cart filters or POS for order entry and its report."
    ],
    "troubleshooting": [
      "No result: clear the group and try a shorter phrase or route; printing follows current filters."
    ]
  },
  {
    "id": "lists",
    "group": "start",
    "group_title": "Getting started",
    "title": "Working with lists and forms",
    "paths": [],
    "paragraphs": [
      "Lists show records in pages. Filters change the result set; row selection prepares bulk actions where supported."
    ],
    "steps": [
      "Enter a search, wait for results and apply filters. Clear both when an expected record is missing.",
      "Use the eye for details, the pencil for editing, and other row actions according to their tooltips and your permissions.",
      "Complete required form fields, save and wait for a success message or field errors.",
      "Retry failed loading. For rejected saves, correct the indicated fields and submit again."
    ],
    "fields": [
      "Status: often means enabled, while a separate schedule shows whether a promotion is running, scheduled or expired.",
      "Delete: read the confirmation; recovery is available only on screens that explicitly provide it.",
      "Prices: use three decimal places, for example 4.000."
    ],
    "tips": [
      "A save click is complete only after success is confirmed. Closing early can discard changes.",
      "Linked records may prevent deletion. Read the reason and use deactivation where available and appropriate."
    ],
    "examples": [
      "If an old search hides an order, clear it, reset filters and review page one."
    ],
    "troubleshooting": [
      "Save rejected: read the message and invalid field; keep the form open until the corrected change is saved."
    ]
  },
  {
    "id": "operating-checklist",
    "group": "start",
    "group_title": "Getting started",
    "title": "Where to start: store setup and the daily operating cycle",
    "paths": [],
    "paragraphs": [
      "Use this sequence from store preparation through selling and fulfillment. Search for the detailed screen explanation before performing an unfamiliar step."
    ],
    "steps": [
      "Check the selected store, language, currency and timezone, then assign staff accounts and roles.",
      "Prepare departments, categories, brands, attributes and options before adding products, prices, stock, images, variants or bundle components.",
      "Configure delivery countries, shipping methods, branches and address rates or weight plans. Check a destination in each supported area and branch pickup when available.",
      "Review checkout, tax, payment methods and notification channels. Use approved test settings when testing sales.",
      "Start the day by checking new orders, pending payments, stock shortages, failed notifications and integration errors.",
      "Sell through Orders or POS. Check the customer, items, shipping and total before creation, then follow payment, preparation and delivery separately.",
      "For returns, review the financial refund, returned goods, stock and cashback before considering the process complete.",
      "End the day by reconciling collected and refunded amounts per currency and reviewing unfinished orders and failed background work."
    ],
    "fields": [
      "Store setup: the selected store owns its catalog and stock; these are not automatically copied to another store.",
      "Content: banners, collections and pages control presentation; they do not replace product activation or valid price and stock.",
      "Outcome: a success message followed by persisted data after refresh. A queued job does not mean sync or delivery has completed."
    ],
    "tips": [
      "Use a separate named account for each employee. Audit logs and order entry sales depend on knowing who performed the action."
    ],
    "examples": [
      "POS sale: select customer → add product and variant → choose delivery or pickup → review payment → create order → fulfill and deliver → review the report."
    ],
    "troubleshooting": [
      "An order exists without collected funds: check its payment status and method. Confirmation or an invoice does not prove a COD payment has been collected."
    ]
  },
  {
    "id": "operating-concepts",
    "group": "start",
    "group_title": "Getting started",
    "title": "Status meanings: orders, payments, stock and delivery jobs",
    "paths": [],
    "paragraphs": [
      "Read a status together with the kind of record. Active, successful and confirmed do not mean the same thing across all screens."
    ],
    "steps": [
      "Identify whether you are reviewing a product, order, payment, shipment, message or integration job.",
      "Open the underlying record before making a financial or stock decision; a single badge is insufficient.",
      "After an action check the status, total, reference and activity time, then refresh when waiting for background processing."
    ],
    "fields": [
      "Product status controls publication. Availability also requires sellable product, variant or bundle-component stock.",
      "Order status tracks preparation, shipping, delivery or cancellation separately from payment status.",
      "Payment status describes collected, pending or refunded funds. The payment method is a separate value.",
      "Item readiness and driver assignment are fulfillment details; they do not automatically record collection or delivery.",
      "Open carts include active and abandoned carts. The inactivity duration is an independent filter.",
      "Queued, scheduled or running does not establish final success.",
      "Incomplete profitability data means something is unknown; unknown must not be treated as zero."
    ],
    "tips": [
      "Read every amount with its currency and every report period with its timezone and date definition. Order sales, collections and contribution margin are different measures."
    ],
    "examples": [
      "A confirmed COD order may be in preparation before collection is recorded. Follow fulfillment and collection as separate steps."
    ],
    "troubleshooting": [
      "A product is visible but cannot be purchased: check product status, variant status and stock, quantity limits and, for a bundle, component availability."
    ]
  },
  {
    "id": "dashboard",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Main dashboard",
    "paths": [
      "/admin/dashboard"
    ],
    "paragraphs": [
      "The dashboard summarizes orders, payments, products, recent activity and operational alerts for the selected store."
    ],
    "steps": [
      "Check the store, then choose dates and currency where provided.",
      "Read each card label to distinguish counts, collected money and net collections after refunds.",
      "Follow its detail link and check the filters on the destination screen.",
      "Open individual recent orders, payments or alerts when investigating a total."
    ],
    "fields": [
      "Collected: confirmed payment amounts in the reporting period.",
      "Refunded and net collections: net subtracts recognized refunds; it is not product profit.",
      "Low stock: active products with five units or fewer."
    ],
    "tips": [
      "Compare the same dates, timezone and currency. Different currencies must remain separate.",
      "Cards and destination links can depend on your screen permissions."
    ],
    "examples": [
      "Before comparing daily collections, use the same KWD period in Financial overview and review linked payments."
    ],
    "troubleshooting": [
      "A card is absent: check access to its target report or list, not only record counts."
    ]
  },
  {
    "id": "reports",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Reports center",
    "paths": [
      "/admin/reports"
    ],
    "paragraphs": [
      "The center links to reports your account can open. Choose a report according to the question you are investigating."
    ],
    "steps": [
      "Decide whether you need finance, inventory, customer or marketing information.",
      "Open its card and set the available dates, currency and filters.",
      "Compare equivalent periods in the same currency and follow record links when available."
    ],
    "fields": [
      "Financial reports: collections, refunds, net amounts, payment statuses and gateway performance. Profitability explains contribution after recorded product costs and direct expenses.",
      "Operational reports: inventory, stock alerts, customers, sources, search and marketing."
    ],
    "tips": [
      "Each report has its own screen permission, so available cards differ between staff accounts.",
      "Use the displayed reporting timezone when comparing dates."
    ],
    "examples": [
      "Use Order entry sales for who entered an order and Payments to investigate collected funds."
    ],
    "troubleshooting": [
      "An empty report requires checking store, dates, currency and status definitions before concluding there were no sales."
    ]
  },
  {
    "id": "staff-sales-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Order entry sales, including staff with zero sales",
    "paths": [
      "/admin/reports/staff-sales"
    ],
    "paragraphs": [
      "Reports → Order entry sales groups POS orders by the employee who created the order, not its customer. Access requires reports.staff_sales.view."
    ],
    "steps": [
      "Check the store and choose From and To in its timezone; enter a currency to limit the results.",
      "Leave Entered by on All users or select an individual employee, including one who has never entered an order.",
      "Review order, sales-order, cancelled and refunded counts and compare Total sales with Total order amount.",
      "Read each currency separately. Staff without matching orders remain visible with zero counts and 0.000 amounts.",
      "Use financial reports and Payments to review actual collections for a comparable period and currency; this report sums order values."
    ],
    "fields": [
      "Orders: matching POS orders, including cancelled and fully refunded orders.",
      "Sales orders and Total sales: exclude cancelled and fully refunded order statuses, but may include orders whose payment has not been collected.",
      "Total order amount: matching values from all statuses, including cancellation and full refund.",
      "Users: the displayed employee count, including zero rows; Not recorded is not an identified employee.",
      "Staff: current store assignments plus historical creators of its POS orders, preserving available historical names.",
      "Not recorded: an older POS order without a saved creator. It is not attributed to the customer or guessed employee."
    ],
    "tips": [
      "This report does not change salary, commission or order status. Permission to create an order does not automatically grant report access."
    ],
    "examples": [
      "An employee has a confirmed 9.000 order and a cancelled 3.000 KWD order: Orders = 2, Sales orders = 1, Total sales = 9.000, Total order amount = 12.000. Another employee with no orders shows 0.000."
    ],
    "troubleshooting": [
      "An employee shows zero: check dates, currency and whether the order was created in POS by that account. Website and app orders are not manually entered sales for that employee.",
      "The report is missing: check its specific screen permission and the employee’s store assignment. The general reports permission alone is insufficient."
    ]
  },
  {
    "id": "reports-reading",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Choosing the right report and comparing figures",
    "paths": [],
    "paragraphs": [
      "Choose the report by the question, then align store, period, currency and date definition. Different reports can legitimately measure different amounts."
    ],
    "steps": [
      "Use Order entry sales to identify POS order creators; use Order sources for website, iOS, Android or POS origins.",
      "Use Customer sources and devices for customer registration origin and latest device, not the origin of an individual order.",
      "Use Financial overview, Payments, Gateway breakdown and Refunds for collected, refunded and net collected funds.",
      "Use Profitability for contribution after costs and inspect data quality before interpreting the result.",
      "Use Inventory and Stock alerts for quantity and availability, and Search analytics for search performance.",
      "Before comparing, check the report’s date basis, currency, timezone and filters, then refresh both results."
    ],
    "fields": [
      "Order sales are order values under the report’s rules and can include unpaid orders.",
      "Collected funds are successful payment amounts under the report’s period and definition.",
      "Net collection subtracts approved refunds, not automatically product costs.",
      "Contribution margin uses recorded revenue, costs, direct expenses and returns with their data quality.",
      "Zero means no matching value, or a staff member without orders in the entry report. Unknown and incomplete mean something different.",
      "Order source describes a purchase. Customer registration source and latest device describe account activity."
    ],
    "tips": [
      "Do not guess iPhone or Android origins for unidentified historical data. Reports cannot reconstruct device activity that was never recorded."
    ],
    "examples": [
      "An unpaid 10.000 POS order can count in its creator’s sales but not successful collections. An October order paid in November can belong to different periods depending on the report."
    ],
    "troubleshooting": [
      "Figures differ: compare definitions, order and payment statuses, creation, collection and refund dates, currencies and filters before changing any underlying record."
    ]
  },
  {
    "id": "profitability-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Profitability and contribution report",
    "paths": [
      "/admin/reports/profitability"
    ],
    "paragraphs": [
      "Open Reports then Profitability to review order or product contribution for the selected store. The screen requires reports.profitability.view. Contribution deducts recorded product costs and direct expenses; it is not accounting net profit after overheads such as salaries and rent.",
      "The period selects orders by their creation date that reached delivered status, using the displayed store timezone. Refunds and cost corrections recorded later still affect their original orders through the check time, so refreshing an older period can change its results.",
      "Currencies remain separate and amounts use three decimal places. Read data quality alongside contribution: an unknown amount is not zero, and negative contribution remains visible for investigation."
    ],
    "steps": [
      "Check the selected store, then open Reports → Profitability. Seeing and opening the report requires its own screen permission, rather than general report access alone.",
      "Set From and To, and enter a currency code such as KWD to filter to one currency. Results update when filters change; the list returns to its first page and any selected order details close.",
      "Start with each currency summary. Check counts of complete, estimated and incomplete orders and complete data coverage before relying on contribution totals.",
      "Select Orders to see order number, currency, net revenue before refunds, product costs, recovered goods cost, direct expenses, contribution and data quality. Lists use pages of 25 rows; use Previous and Next for the remaining results.",
      "Click Details beside an order to inspect data issues, revenue allocation, allocated and unallocated refunds, cashback, units restored to stock and each line calculation. Click Details again to close it.",
      "Open the order number to review its records and costs if you have orders.view. Within the order, viewing internal order costs requires orders.costs.view and recording or correcting costs requires orders.costs.manage.",
      "For missing costs, review each unit cost and the direct expenses for actual shipping and payment fees. Record the correct amount in the order currency with a reason, marking it Estimated only when unconfirmed. If an expense category genuinely has no cost, record an explicit zero instead of leaving it unrecorded.",
      "Return to the report and click Refresh after correcting costs, completing a refund or inspecting a return. Review the new check time and data quality; the report itself is read-only and does not change orders or stock.",
      "Select Products to compare product or variant, SKU and currency, then inspect quantity, product net revenue, allocated refunds, sold goods cost, recovered goods cost and margin. Switching views returns to the first page and closes order details.",
      "Click Export CSV to download all matching rows for the selected period, currency and view, rather than only the current page. Export is disabled while loading or when there are no rows; inspect the error message if the download fails."
    ],
    "fields": [
      "From / To and timezone: the creation-date range of orders that reached delivery, rather than a payment collection period or a refund processing period alone.",
      "Currency: a three-letter code such as KWD or EGP. Leaving it blank does not convert currencies into one total; read each currency summary independently.",
      "Checked at: when the displayed results were calculated. A later refund or correction can change the same period after a refresh.",
      "Contribution of complete orders: the sum for orders classified Complete only. If none qualify, the screen says No complete orders rather than claiming a confirmed zero profit total.",
      "Complete data coverage: complete orders divided by all included orders, shown as a count and percentage. For example, 8 of 10 means 80% coverage, not an 80% profit margin.",
      "Data quality: Complete for confirmed required data, Estimated when an estimate or estimated allocation is used, and Incomplete when necessary data is missing or conflicting. Estimated-order contribution is shown separately from complete contribution.",
      "Net revenue before refunds: order revenue after discounts and excluding tax according to saved financial data, before deducting refunds. It differs from cash collected during the period.",
      "Product costs / Known product costs: sold quantities valued using saved historical unit costs or documented corrections. A known subtotal does not prove every line has a cost; sale prices are not used to guess missing costs.",
      "Recorded direct expenses: actual shipping cost, payment gateway fees and other direct expenses recorded for the order. Shipping charged to the customer is revenue and differs from the courier cost.",
      "Issued cashback less reversals: cashback actually issued after valid reversal entries. A promise of cashback alone is not a confirmed issued expense.",
      "Successful gross refunds / Net refunds: gross includes refund tax, while net excludes it according to saved data. Contribution deducts net refunds once.",
      "Net refunds allocated to products: the portion assigned to product lines. Unallocated net refunds remain at order level; do not allocate them a second time when comparing margins.",
      "Pending refunds (not deducted): amounts not yet recognized as successful refunds. They are disclosed for follow-up and are not deducted as completed refunds.",
      "Recovered goods cost / Units restored to stock: the recovered cost of resellable units actually returned to stock. Damaged units recover no cost, and a financial refund alone does not prove stock was restored.",
      "Revenue not allocated to products: order-level revenue such as shipping or amounts that cannot be allocated reliably to lines. Costs without allocated product revenue disclose costs lacking corresponding allocated revenue in the product view.",
      "Product revenue allocation: saved tax data for each line may be used. For older orders, allocation may be estimated in proportion to saved line totals or quantities; amounts remain at order level when reliable allocation is unavailable.",
      "Order contribution = net revenue before refunds − net refunds − sold goods cost + recovered goods cost − direct expenses − (issued cashback − valid reversals).",
      "Product margin = product net revenue − its allocated net refunds − its sold goods cost + its recovered goods cost. It excludes order shipping revenue, direct expenses, cashback and unallocated refunds."
    ],
    "tips": [
      "Example in KWD: net revenue 100.000 − net refunds 10.000 − product costs 60.000 + recovered goods cost 6.000 − direct expenses 5.000 − cashback 2.000 = order contribution 29.000 before overheads, provided the data is complete.",
      "Do not combine currency summaries or treat known amounts as a complete profit total. Estimated and incomplete orders are excluded from Contribution of complete orders.",
      "Product margins alone do not equal order contribution. Reconcile unallocated order revenue, direct expenses, cashback and unallocated refunds; do not subtract a product refund again because its margin already includes it.",
      "For Unknown or Incomplete, open Details and read the issue: missing unit cost, unrecorded shipping or payment fees, refund currency or tax conflicts, or inconsistent return or wallet records. Correct the source and refresh; do not replace unknown values with zero to improve the result.",
      "If a saved unit cost combines goods with an additional service without separating them, recoverable goods cost may remain unconfirmed until correctly documented. Do not assume the service cost is recovered with the goods.",
      "For no results, check the store, order creation date, currency and whether the order reached delivery. Being paid or processing alone does not ensure inclusion.",
      "If cost storage is not installed, an administrator must prepare the required database updates for the affected tenant. Changing current product prices does not automatically complete historical order costs.",
      "For a loading failure, use Retry and read the displayed error. A 404 or absent report endpoint may mean the API version does not yet support Profitability; the admin screen alone is insufficient. Changing filters does not repair a missing API endpoint.",
      "Find this explanation in User guide by searching Profitability, contribution or recovered goods cost. The control panel assistant uses the same explanation."
    ],
    "examples": [
      "An estimated result with missing costs is not complete contribution; inspect data quality and coverage."
    ],
    "troubleshooting": [
      "An old period changed: inspect later refunds, cost corrections or stock returns on the original orders and the calculation time."
    ]
  },
  {
    "id": "financial-overview",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Financial overview",
    "paths": [
      "/admin/reports/financial-overview"
    ],
    "paragraphs": [
      "Use this screen as the reference for period totals, grouped by currency: collected, refunded and net collections."
    ],
    "steps": [
      "Set the available start date, end date and currency filters.",
      "Read each currency separately and compare payment counts with monetary amounts.",
      "Investigate differences in status, gateway or refund reports using the same period."
    ],
    "fields": [
      "Collected: confirmed money received; creating an order does not itself collect money.",
      "Refunded: refunds recognized by their processing state and period.",
      "Net: collected minus refunded, before product costs or operating expenses."
    ],
    "tips": [
      "An older order can be paid during the current period. Created-order counts and payment counts can therefore differ."
    ],
    "examples": [
      "Compare collected, refunded and net amounts in one currency; use Profitability for the separate cost question."
    ],
    "troubleshooting": [
      "Net collection is below sales: inspect collection and refund definitions, payment states and dates before assuming funds are missing."
    ]
  },
  {
    "id": "financial-trend",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Financial trend",
    "paths": [
      "/admin/reports/financial-trend"
    ],
    "paragraphs": [
      "This report places collections, refunds and net amounts on a timeline to explain changes in activity."
    ],
    "steps": [
      "Choose the period, currency and available time grouping.",
      "Read the chart alongside the table and compare series within the same time bucket.",
      "For an empty report, widen the dates or change currency; use the overview for totals."
    ],
    "fields": [
      "Period: the time bucket used by the report.",
      "Orders: an order count, separate from collected value.",
      "Collected, refunded and net: distinct monetary series in the same currency."
    ],
    "tips": [
      "Net collections can fall because refunds increased even when collections stayed steady."
    ],
    "examples": [
      "Compare equal-length periods using the same currency and displayed time grouping; do not add KWD to EGP."
    ],
    "troubleshooting": [
      "A day differs from your device clock: use the store timezone and displayed date boundaries."
    ]
  },
  {
    "id": "payment-status-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Payment status report",
    "paths": [
      "/admin/reports/payment-status-breakdown"
    ],
    "paragraphs": [
      "Groups payment attempts by status and currency so confirmed collections remain distinct from pending and failed attempts."
    ],
    "steps": [
      "Select dates and currency, then review counts and original amounts by status.",
      "Compare shares of count and amount; one large payment can affect value more than volume.",
      "Use the payments list with equivalent filters to investigate individual attempts."
    ],
    "fields": [
      "Original amount: attempted amounts in the group, not necessarily collected money.",
      "Shares: each status proportion of report counts or amounts.",
      "Refunded: refunds associated with the group under the report rules."
    ],
    "tips": [
      "Pending and failed attempts are not confirmed collections."
    ],
    "examples": [
      "Pending and successful amounts are not both collected; inspect the relevant payment status."
    ],
    "troubleshooting": [
      "Payment count differs from order count: one order can have multiple attempts; inspect references."
    ]
  },
  {
    "id": "payment-gateway-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Payment gateway report",
    "paths": [
      "/admin/reports/payment-gateway-breakdown"
    ],
    "paragraphs": [
      "Compare gateway counts, failure rates, collections and refunds for the selected period."
    ],
    "steps": [
      "Set dates and currency, then compare gateway rows.",
      "Read failure rate together with attempt count; small samples can distort percentages.",
      "Investigate payments and webhook logs before reviewing gateway configuration with the appropriate permission."
    ],
    "fields": [
      "Gateway: the payment method or provider.",
      "Failure rate: failed attempts as a share of the report data.",
      "Net collections: collections after refunds, not bank settlement or profit."
    ],
    "tips": [
      "Keep currencies separate and investigate evidence before changing provider credentials."
    ],
    "examples": [
      "Compare gateways in the same period and currency and inspect refunds and payment states."
    ],
    "troubleshooting": [
      "A gateway is absent: it may have no matching payments in the period or currency; check the underlying records."
    ]
  },
  {
    "id": "refunds-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Financial refunds report",
    "paths": [
      "/admin/reports/refunds"
    ],
    "paragraphs": [
      "A paginated refund register with payment and order references. Financial overview remains the source of period totals."
    ],
    "steps": [
      "Set dates and currency or search by reason or reference.",
      "Open the refund or linked payment to review its processing state.",
      "Browse remaining pages and return to financial overview for the period total."
    ],
    "fields": [
      "Refund reference: the system or provider transaction reference.",
      "Status: the recorded processing outcome.",
      "Amount: the refund record amount in its currency."
    ],
    "tips": [
      "Adding only the visible page does not total the entire result set."
    ],
    "examples": [
      "Check successful refund status before subtracting it from collections and open its record for detail."
    ],
    "troubleshooting": [
      "Unexpected refund totals: check refund state, processing date, currency and report definition."
    ]
  },
  {
    "id": "search-analytics",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Search analytics",
    "paths": [
      "/admin/reports/search-analytics"
    ],
    "paragraphs": [
      "Shows storefront search terms, search frequency and queries that returned no products."
    ],
    "steps": [
      "Choose dates and review total searches, unique terms and zero-result searches.",
      "Use top terms to understand demand and the zero-result table to find naming or catalog gaps.",
      "Try a term in product search and review product names and searchable attributes before adding inventory."
    ],
    "fields": [
      "Query: the normalized search phrase used in the report.",
      "Average results: average products returned for the term.",
      "Last search: the latest recorded occurrence."
    ],
    "tips": [
      "The report reflects supported recorded storefront searches; missing data does not prove customers never searched elsewhere."
    ],
    "examples": [
      "Frequent zero-result queries can reveal a missing searchable name or attribute value."
    ],
    "troubleshooting": [
      "No data: check the period, store and storefront search recording rather than concluding there were no visits."
    ]
  },
  {
    "id": "inventory-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Inventory report",
    "paths": [
      "/admin/reports/inventory"
    ],
    "paragraphs": [
      "Shows tracked, out-of-stock and low-stock products plus recorded stock value to support replenishment decisions."
    ],
    "steps": [
      "Review summary cards and the out-of-stock or low-stock tables.",
      "Find the SKU and open its product to inspect stock and variants.",
      "Check unit cost before relying on inventory value; make corrections through product editing or the approved integration."
    ],
    "fields": [
      "Low stock: five units or fewer under the report rules.",
      "Units: recorded stock quantity, not units sold.",
      "Inventory value: depends on recorded unit cost rather than retail selling price."
    ],
    "tips": [
      "Variants and package components can affect how product stock is represented."
    ],
    "examples": [
      "Inventory cost value differs from potential retail sales; inspect the column and currency."
    ],
    "troubleshooting": [
      "Unexpected quantity: check variant and component stock and the product’s latest external sync."
    ]
  },
  {
    "id": "stock-alerts-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Notify-when-available report",
    "paths": [
      "/admin/reports/stock-alerts"
    ],
    "paragraphs": [
      "Lists products with customer restock requests, including pending and notified counts."
    ],
    "steps": [
      "Review demand and available stock to prioritize replenishment.",
      "Open a product and its Orders tab for individual stock-alert records.",
      "After replenishment, inspect recorded notification status; a request alone does not prove delivery succeeded."
    ],
    "fields": [
      "Waiting: requests not yet recorded as notified.",
      "Notified: requests with a recorded notification time.",
      "Latest request: the most recent restock request for the product."
    ],
    "tips": [
      "Check the displayed count against the total because the report can show only an initial subset."
    ],
    "examples": [
      "A stock notification request for a particular color variant differs from one for the parent product."
    ],
    "troubleshooting": [
      "No alert received: inspect requested variant, availability, send time, channel and delivery log."
    ]
  },
  {
    "id": "customers-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Customers report",
    "paths": [
      "/admin/reports/customers"
    ],
    "paragraphs": [
      "Summarizes new, repeat and top-spending customers in the selected store and period."
    ],
    "steps": [
      "Select dates and any available currency filter, then read the customer cards.",
      "Compare new and repeat counts and open a top customer to review orders.",
      "Match spending to the underlying orders before using it for customer follow-up."
    ],
    "fields": [
      "New and repeat: the report classifications for the chosen period.",
      "Orders: the orders included in the report aggregation.",
      "Spending: an amount in the report currency, not wallet balance."
    ],
    "tips": [
      "Customer detail totals can differ when their date scope or definition differs."
    ],
    "examples": [
      "Use the correct customer period, then inspect individual orders rather than treating customer count as purchase count."
    ],
    "troubleshooting": [
      "Customer spending is not wallet balance; they are different measures backed by separate records."
    ]
  },
  {
    "id": "order-platforms-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Order sources report",
    "paths": [
      "/admin/reports/order-platforms"
    ],
    "paragraphs": [
      "Shows the channels or platforms recorded when orders were created."
    ],
    "steps": [
      "Choose dates and available filters, then compare sources.",
      "Read counts and monetary figures within the same currency.",
      "Inspect an individual order for unexpected sources rather than using the customer current device as evidence."
    ],
    "fields": [
      "Source: the recorded order creation channel.",
      "Unknown: no classifiable source was recorded."
    ],
    "tips": [
      "Order source differs from customer registration source and the device most recently used."
    ],
    "examples": [
      "One customer can buy through web and app; read each order’s own origin."
    ],
    "troubleshooting": [
      "Unknown origin means the old record has no saved classification; do not hide it by inventing a source."
    ]
  },
  {
    "id": "customer-sources-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Customer sources report",
    "paths": [
      "/admin/reports/customer-sources"
    ],
    "paragraphs": [
      "Reviews recorded customer acquisition sources while distinguishing original source from current device activity."
    ],
    "steps": [
      "Choose dates and review customer source distribution.",
      "Open customer details to inspect registration, activity and orders.",
      "Read the current-device hint before treating it as the registration device."
    ],
    "fields": [
      "Customer source: the recorded account source used by the report.",
      "Current device: the last device observed in this store, with its recorded activity time.",
      "Unknown: source or device information is unavailable."
    ],
    "tips": [
      "A new current device does not rewrite the original registration source."
    ],
    "examples": [
      "A customer registered on Android and later used the web; registration origin and latest device can legitimately differ."
    ],
    "troubleshooting": [
      "Unknown latest device: inspect recorded activity; having a phone number does not establish device type."
    ]
  },
  {
    "id": "marketing-report",
    "group": "reports",
    "group_title": "Dashboard and reports",
    "title": "Marketing report",
    "paths": [
      "/admin/reports/marketing"
    ],
    "paragraphs": [
      "Combines promotion usage, discount and cashback amounts, plus open and abandoned carts."
    ],
    "steps": [
      "Choose dates and review usage, discounts and cashback.",
      "Inspect the promotion table and its usage records for related orders.",
      "Review abandoned carts from their own screen; an open cart is not a paid order."
    ],
    "fields": [
      "Discount: reductions recorded in promotion usages.",
      "Cashback: a recorded reward rather than an immediate price reduction.",
      "Abandoned cart value: value in carts that did not become completed orders."
    ],
    "tips": [
      "Do not add cart value to collected sales. Financial overview reports actual collections."
    ],
    "examples": [
      "Review promotion usage and discounts; use the cart screen for activity filters on recent open carts."
    ],
    "troubleshooting": [
      "Cart counts differ from the open-cart list: the marketing report counts Abandoned status, while the follow-up list can also include Active carts."
    ]
  },
  {
    "id": "catalog",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Products list, search and bulk actions",
    "paths": [
      "/admin/catalog/products"
    ],
    "paragraphs": [
      "Start here to find, edit or group products for a temporary campaign. Filters and selection alone do not change prices."
    ],
    "steps": [
      "Search by product name or SKU and apply department, category, brand, status or stock filters.",
      "For an attribute search, choose the attribute and enter its value. Combined filters narrow the results.",
      "Open details with the eye, edit with the pencil, or add a new product.",
      "Select rows or select all search results across pages within the allowed limit.",
      "To combine groups, change filters and add search results to the selection, then review the selected count before confirming a bulk action."
    ],
    "fields": [
      "Selection: can include earlier searches when results were appended.",
      "Attribute and value: leaving value empty finds products carrying the chosen store attribute.",
      "Export: choose all, active or low-stock products in the export dialog."
    ],
    "tips": [
      "Viewing products does not grant bulk editing, campaign or export permissions.",
      "Campaign selection is limited to 20,000 products and becomes a fixed product set; future filter matches are not enrolled automatically."
    ],
    "examples": [
      "Search a specific SKU before creating a duplicate, then open Details to inspect stock and variants."
    ],
    "troubleshooting": [
      "No results after attribute filtering: review department, attribute, value, status and any remaining search."
    ]
  },
  {
    "id": "product-form",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Create and edit products: identity, content and classification",
    "paths": [
      "/admin/catalog/products/new",
      "/admin/catalog/products/:id/edit"
    ],
    "paragraphs": [
      "The form uses tabs. Save identity, relationships and pricing first so images and variants can use the new product record."
    ],
    "steps": [
      "Enter Arabic and English names, slug, SKU and an optional barcode under identity.",
      "Write short and full descriptions for each language; translations are not automatic.",
      "Choose departments, categories, subcategories, brand, tags and tax class.",
      "Set price, stock and status, then save and wait for confirmation.",
      "Return to the saved product for images, attributes, variants and related products."
    ],
    "fields": [
      "Slug and SKU: identifiers subject to store validation and uniqueness rules.",
      "Relationships: multiple classifications are supported; choosing children adds their parents.",
      "Related products: similar, complementary or higher-tier products from the same store; self-links are rejected.",
      "SEO: translated meta titles and descriptions."
    ],
    "tips": [
      "Remove selected children before removing their parent department or category.",
      "Drafts are hidden from customers. Choose active and save to publish."
    ],
    "examples": [
      "A bilingual product needs content in both languages; saving Arabic does not create an English translation."
    ],
    "troubleshooting": [
      "A classification is missing: check its parent, store and active status, then refresh available choices."
    ]
  },
  {
    "id": "product-pricing",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product pricing, stock and purchase limits",
    "paths": [],
    "paragraphs": [
      "The pricing tab controls normal selling prices, costs and quantity limits. Temporary campaigns overlay current prices without replacing stored originals."
    ],
    "steps": [
      "Open the product edit screen and its pricing and stock tab.",
      "Enter base price, optional cost, stock and weight.",
      "For a manual markdown, set base price to the selling price and old price to the higher comparison price. Use a temporary campaign for a scheduled offer.",
      "Set quantity limits, status, order and merchandising flags, then save."
    ],
    "fields": [
      "Base price: normal selling price before a temporary catalog campaign.",
      "Old price: comparison price when valid and greater than the selling price.",
      "Cost: internal input for stock valuation, separate from selling price.",
      "Minimum and maximum order quantity: product quantity limits within an order.",
      "Per-customer maximum: cumulative customer purchase limit; blank means unlimited."
    ],
    "tips": [
      "Check variant prices and quantities separately when variants exist.",
      "A manual price change has no automatic end date or restoration."
    ],
    "examples": [
      "A sale price of 8.000 and compare-at price of 10.000 show a price difference; compare-at is not product cost."
    ],
    "troubleshooting": [
      "A manual price does not revert when a campaign ends; inspect which price field was edited and whether another campaign applies."
    ]
  },
  {
    "id": "catalog-availability",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product availability, stock shortages and external stock sync",
    "paths": [],
    "paragraphs": [
      "Availability follows the current status and the stock appropriate to the product type. Historical import data is not the daily control for enabling sales."
    ],
    "steps": [
      "Identify whether the item is a simple product, a product with variants or a bundle.",
      "For a simple product check its status and stock. For variants check the selected variant’s activation and stock rather than relying on the parent quantity.",
      "For a bundle check each component, its variant and the required quantity per bundle.",
      "After removing variants to return to a simple product, review the parent’s own price and stock, save and check the storefront.",
      "If quantities change again, inspect external stock updates, the product log and the latest sync before changing settings.",
      "Check Show out-of-stock products to understand whether unavailable items are hidden or visible without purchase."
    ],
    "fields": [
      "Active controls publication; it cannot replace missing stock or an unavailable variant.",
      "Variant stock is the quantity for the selected sellable version; do not count parent and variant stock as two supplies for the same sale.",
      "Bundle availability depends on its components and required quantities; one component can make the bundle unavailable.",
      "External stock updates can overwrite quantity from the configured source during sync; inspect the direction and latest result.",
      "Notify me when available records interest; it does not reserve stock.",
      "Service products follow different stock handling from counted physical goods; do not apply the ordinary zero-stock interpretation without checking product type."
    ],
    "tips": [
      "Do not disable sync to mask an unexplained quantity mismatch. Also check per-order and per-customer quantity limits when cart addition is rejected."
    ],
    "examples": [
      "A bundle needs two A books and one B book. A stock of 8 and B stock of 3 allows 3 bundles because B is the limiting component."
    ],
    "troubleshooting": [
      "Changing to Active is followed by Out of stock: inspect quantity, variants and external update logs; repeatedly changing status does not fix the quantity source.",
      "Stock exists but the product is missing: review publication status, filters, classifications, selected store and storefront rules."
    ]
  },
  {
    "id": "product-images",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product images and YouTube video",
    "paths": [],
    "paragraphs": [
      "The Images tab manages product pictures and the primary image. Save a new product before uploading or copying media."
    ],
    "steps": [
      "Open a saved product and its Images tab.",
      "Upload a file or copy from the media library and wait for the new image.",
      "Use the star to set the primary image and check its badge.",
      "Add a supported YouTube URL, inspect the preview and save product details.",
      "Read the confirmation before deleting an image.",
      "Select multiple images in one upload, review each result, then drag images into order and wait for the reorder save result."
    ],
    "fields": [
      "Primary image: the product default; a variant can have its own optional image.",
      "Video URL: supported youtube.com or youtu.be watch, Shorts and embed links.",
      "Image order controls the gallery sequence. Selecting the primary image with the star is a separate action."
    ],
    "tips": [
      "Deleting an image differs from changing which image is primary.",
      "If a preview is missing, check upload completion and errors before uploading again."
    ],
    "examples": [
      "Upload three images, choose the primary one, reorder the gallery and verify after reopening."
    ],
    "troubleshooting": [
      "Image order reverted: check the reorder result and upload errors; image operations and product-field saving are separate."
    ]
  },
  {
    "id": "product-detail",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product details, demand and reviews",
    "paths": [
      "/admin/catalog/products/:id"
    ],
    "paragraphs": [
      "Inspect product information, images, variants, ratings and demand without editing the record."
    ],
    "steps": [
      "Open the eye action and review price, stock, status and relationships.",
      "Use variants or matrix tabs according to your permissions.",
      "Open Orders for the latest ten orders, quantities and restock requests.",
      "Review rating distribution and follow the all-reviews link for moderation.",
      "Review external update logs for the source and available field changes before editing externally synchronized data."
    ],
    "fields": [
      "Latest ten orders: a recent sample, not complete product sales history.",
      "Restock requests: customer contact, variant, request time and notification time when recorded.",
      "Verified purchases: reviews linked to recorded purchases under review rules."
    ],
    "tips": [
      "Administrative prices are management data. Use campaign preview and the storefront consuming catalog prices to review the customer offer experience."
    ],
    "examples": [
      "Recent product orders are a sample; a complete sales comparison needs the appropriate report period."
    ],
    "troubleshooting": [
      "A value changed without your edit: inspect external update and audit logs before overwriting it."
    ]
  },
  {
    "id": "variants",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product variants: combinations, prices and stock",
    "paths": [
      "/admin/catalog/products/:id/variants",
      "/admin/catalog/products/:id/variants/new",
      "/admin/catalog/products/:id/variants/:variantId/edit"
    ],
    "paragraphs": [
      "A variant is a sellable option combination, such as a large red shirt, with its own price, stock and optional image."
    ],
    "steps": [
      "Create store options and values first, then open product variants or the embedded editor.",
      "Add a variant and choose one value for each required option.",
      "Enter SKU, barcode, selling and comparison prices, cost, stock, weight, order and status.",
      "Choose an optional variant image, save and check the combination in the list.",
      "Edit existing details with the pencil; create a new variant when a different combination is needed."
    ],
    "fields": [
      "Combination: locked after creation.",
      "Variant image: used when selected; otherwise the product primary image is the fallback.",
      "Price and stock: review each variant independently."
    ],
    "tips": [
      "Deletion can be rejected for variants in active carts. Duplicate combinations are not valid.",
      "A catalog campaign includes the product variants and discounts each variant own price."
    ],
    "examples": [
      "A large red shirt has its own SKU and stock, separate from a small blue variant."
    ],
    "troubleshooting": [
      "Variant deletion rejected: check active-cart dependencies and the stated reason rather than duplicating the combination."
    ]
  },
  {
    "id": "variant-matrix",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Variant matrix",
    "paths": [
      "/admin/catalog/products/:id/variants/matrix"
    ],
    "paragraphs": [
      "Generate and inspect multiple option combinations instead of creating every variant separately."
    ],
    "steps": [
      "Open the saved product matrix and choose generation options. Blank selection uses the matrix defaults described by the screen.",
      "Choose create missing to preserve existing combinations, or fail if exists when conflicts should stop generation.",
      "Enter optional default price and stock, generate or generate missing and inspect created/skipped counts.",
      "Review matrix rows and use each row action to save price, stock or status, waiting for its result."
    ],
    "fields": [
      "Option values: determine the resulting combination set.",
      "Variant row: one independent sellable combination.",
      "Mode: controls existing combinations without deleting them to recreate everything.",
      "Default price and stock: inputs for new combinations; inspect them before selling.",
      "Variant search helps find names, SKU, barcode or option values; confirm the parent product before editing a row."
    ],
    "tips": [
      "Many selected values can create many combinations. Review the count and do not assume generated prices or stock are already correct."
    ],
    "examples": [
      "Three colors and two sizes yield up to six combinations; create-missing preserves existing variants."
    ],
    "troubleshooting": [
      "A row will not save: review price, barcode, SKU uniqueness and its row-level error."
    ]
  },
  {
    "id": "product-features",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Packages and attached product services",
    "paths": [],
    "paragraphs": [
      "The package and services tab selects normal or package products and attaches optional services such as wrapping or printing."
    ],
    "steps": [
      "For a package, choose package type and add component products, their variants when applicable and quantities.",
      "Review all components and set the package selling price in pricing.",
      "Select available services, mark required selection where needed and save.",
      "Create missing services on their management screen, then refresh the product service list."
    ],
    "fields": [
      "Package price: the price you enter, not an automatic sum of component prices.",
      "Package stock: derived from components and adjusted through order stock movements.",
      "Service: its selected cost is added per item and can be shared by multiple products."
    ],
    "tips": [
      "Check component variants and quantities carefully.",
      "Catalog price campaign discounts do not reduce additional service charges."
    ],
    "examples": [
      "A 9.000 bundle with 1.000 wrapping per unit is separate from the component catalog prices."
    ],
    "troubleshooting": [
      "A bundle cannot be added: inspect each component and variant activation and the quantity required per bundle."
    ]
  },
  {
    "id": "departments",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Departments: list, create and edit",
    "paths": [
      "/admin/catalog/departments",
      "/admin/catalog/departments/new",
      "/admin/catalog/departments/:id/edit"
    ],
    "paragraphs": [
      "Organize the store catalog using searchable records, status filters and available row actions."
    ],
    "steps": [
      "Search for an existing record before creating a similar one.",
      "Add or edit a record and enter translated names and slug.",
      "Attach attributes to a department so they appear on its products; create missing attributes first.",
      "Complete the available description, media, display order, status and SEO fields, then save and wait for confirmation."
    ],
    "fields": [
      "Translated name: the label shown in the storefront language.",
      "Slug: the URL identifier, subject to validation and uniqueness.",
      "Display order: controls presentation where the storefront uses it.",
      "Status: inactive records are hidden according to their storefront use.",
      "Show on home is independent of activation and selects departments for the Kalemat home row."
    ],
    "tips": [
      "Consider linked products before deactivation. Linked records may prevent deletion; read the rejection reason."
    ],
    "examples": [
      "A Books department can use an Author attribute on its products."
    ],
    "troubleshooting": [
      "A department is missing from home: check Active and Show on home separately."
    ]
  },
  {
    "id": "categories",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Categories: list, create and edit",
    "paths": [
      "/admin/catalog/categories",
      "/admin/catalog/categories/new",
      "/admin/catalog/categories/:id/edit"
    ],
    "paragraphs": [
      "Organize the store catalog using searchable records, status filters and available row actions."
    ],
    "steps": [
      "Search for an existing record before creating a similar one.",
      "Add or edit a record and enter translated names and slug.",
      "Choose the parent department before saving and filter by department when finding a category.",
      "Complete the available description, media, display order, status and SEO fields, then save and wait for confirmation."
    ],
    "fields": [
      "Translated name: the label shown in the storefront language.",
      "Slug: the URL identifier, subject to validation and uniqueness.",
      "Display order: controls presentation where the storefront uses it.",
      "Status: inactive records are hidden according to their storefront use.",
      "Show on home is independent of activation and selects categories for the Kalemat home row."
    ],
    "tips": [
      "Consider linked products before deactivation. Linked records may prevent deletion; read the rejection reason."
    ],
    "examples": [
      "A Novels category belongs to its selected parent department; confirm that parent before saving a similar name."
    ],
    "troubleshooting": [
      "Missing category products: inspect relationships, publication and stock filtering."
    ]
  },
  {
    "id": "catalog-home-visibility",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Department and category visibility on the Kalemat home page",
    "paths": [],
    "paragraphs": [
      "Show on home selects departments and categories for Kalemat’s home page. Activation and home-page visibility are separate settings."
    ],
    "steps": [
      "Open a department or category and review its translated name, image, order and active status.",
      "Set Show on home, save and wait for success.",
      "Refresh the correct store home page in the desired language.",
      "Selected items use two rows of cards; additional items scroll horizontally in both directions.",
      "If a line has no eligible items, check the selected active records rather than expecting an empty heading."
    ],
    "fields": [
      "Active controls ordinary storefront availability of the record.",
      "Show on home selects its home-page card without replacing activation.",
      "Order and image follow the storefront layout; a fallback icon can appear when an image is absent.",
      "Column count adapts to screen width while retaining two rows and horizontal overflow."
    ],
    "tips": [
      "Changing one store’s classifications does not change another store. Product collections are configured independently in Content."
    ],
    "examples": [
      "Hide an active category from home to remove its home card while retaining its other supported uses."
    ],
    "troubleshooting": [
      "A saved record is missing from home: check store, activation and Show on home, refresh and allow cached public data to update when applicable."
    ]
  },
  {
    "id": "subcategories",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Subcategories: list, create and edit",
    "paths": [
      "/admin/catalog/subcategories",
      "/admin/catalog/subcategories/new",
      "/admin/catalog/subcategories/:id/edit"
    ],
    "paragraphs": [
      "Organize the store catalog using searchable records, status filters and available row actions."
    ],
    "steps": [
      "Search for an existing record before creating a similar one.",
      "Add or edit a record and enter translated names and slug.",
      "Filter by department and choose the parent category; matching names alone do not identify the correct parent.",
      "Complete the available description, media, display order, status and SEO fields, then save and wait for confirmation."
    ],
    "fields": [
      "Translated name: the label shown in the storefront language.",
      "Slug: the URL identifier, subject to validation and uniqueness.",
      "Display order: controls presentation where the storefront uses it.",
      "Status: inactive records are hidden according to their storefront use."
    ],
    "tips": [
      "Consider linked products before deactivation. Linked records may prevent deletion; read the rejection reason."
    ],
    "examples": [
      "Choose department, category and subcategory to reach the correct branch."
    ],
    "troubleshooting": [
      "Wrong parent: correct the selection and review affected product relationships after saving."
    ]
  },
  {
    "id": "brands",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Brands: list, create and edit",
    "paths": [
      "/admin/catalog/brands",
      "/admin/catalog/brands/new",
      "/admin/catalog/brands/:id/edit"
    ],
    "paragraphs": [
      "Organize the store catalog using searchable records, status filters and available row actions."
    ],
    "steps": [
      "Search for an existing record before creating a similar one.",
      "Add or edit a record and enter translated names and slug.",
      "Enter the logo URL in its field, then assign the brand from product editing.",
      "Complete the available description, media, display order, status and SEO fields, then save and wait for confirmation."
    ],
    "fields": [
      "Translated name: the label shown in the storefront language.",
      "Slug: the URL identifier, subject to validation and uniqueness.",
      "Display order: controls presentation where the storefront uses it.",
      "Status: inactive records are hidden according to their storefront use."
    ],
    "tips": [
      "Consider linked products before deactivation. Linked records may prevent deletion; read the rejection reason."
    ],
    "examples": [
      "Rename an existing brand rather than creating one record per product."
    ],
    "troubleshooting": [
      "Brand deletion rejected: inspect dependencies and the message before removing relationships."
    ]
  },
  {
    "id": "tags",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Tags: list, create and edit",
    "paths": [
      "/admin/catalog/tags",
      "/admin/catalog/tags/new",
      "/admin/catalog/tags/:id/edit"
    ],
    "paragraphs": [
      "Organize the store catalog using searchable records, status filters and available row actions."
    ],
    "steps": [
      "Search for an existing record before creating a similar one.",
      "Add or edit a record and enter translated names and slug.",
      "Assign tags in the product form for merchandising labels beyond the main classification.",
      "Complete the available description, media, display order, status and SEO fields, then save and wait for confirmation."
    ],
    "fields": [
      "Translated name: the label shown in the storefront language.",
      "Slug: the URL identifier, subject to validation and uniqueness.",
      "Display order: controls presentation where the storefront uses it.",
      "Status: inactive records are hidden according to their storefront use."
    ],
    "tips": [
      "Consider linked products before deactivation. Linked records may prevent deletion; read the rejection reason."
    ],
    "examples": [
      "A Gift tag can group products across categories without moving their classifications."
    ],
    "troubleshooting": [
      "Tag missing: check product assignment, language, activation and storefront support."
    ]
  },
  {
    "id": "product-options",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product options and values",
    "paths": [
      "/admin/catalog/product-options",
      "/admin/catalog/product-options/new",
      "/admin/catalog/product-options/:id/edit"
    ],
    "paragraphs": [
      "Options such as color and size contain values such as red, blue, small and large. They belong to the store and can serve multiple products."
    ],
    "steps": [
      "Create the translated option and its type, then save it first.",
      "Add values with names, code, order, status and color code where appropriate.",
      "Create product variants using those values.",
      "Edit a value in its editor, update it and inspect the saved table."
    ],
    "fields": [
      "Option type: controls value presentation or use.",
      "Color code: a visual color value, separate from its translated name.",
      "Option value: one part of a variant combination."
    ],
    "tips": [
      "Values used by variants may not be deleted. Descriptive information such as author normally belongs in attributes."
    ],
    "examples": [
      "Color values Red and Blue can create sellable variants, unlike descriptive attributes with no separate stock."
    ],
    "troubleshooting": [
      "An option value is unavailable: check option, values, activation and store before recreating it."
    ]
  },
  {
    "id": "product-attributes",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product attributes and value search",
    "paths": [
      "/admin/catalog/product-attributes",
      "/admin/catalog/product-attributes/new",
      "/admin/catalog/product-attributes/:id/edit"
    ],
    "paragraphs": [
      "Attributes describe author, material or packaging. They can use free text or a choice list and are attached to departments."
    ],
    "steps": [
      "Create a translated name, code and type, assign departments and save.",
      "Add choice values for list attributes; enter free-text values on products.",
      "Complete values on an eligible product. With permission, attributes can also be created or edited in its Attributes tab.",
      "Enable filter visibility or keyword search in values according to the intended use.",
      "For a campaign targeting a value, filter the products list by attribute and value, then select the results."
    ],
    "fields": [
      "Departments: determine which products expose the attribute.",
      "Filter visibility: exposes the attribute in supported storefront filters.",
      "Keyword search: allows Arabic or English attribute values to match storefront searches.",
      "List values can be edited rather than duplicated; check their code, translations and order using the displayed fields."
    ],
    "tips": [
      "Attributes do not create independent SKU or stock records. Use variants for independent sellable combinations."
    ],
    "examples": [
      "Searchable Author values help find a book without creating another stock variant."
    ],
    "troubleshooting": [
      "Attribute search misses a product: check department binding, saved value, search enablement and language."
    ]
  },
  {
    "id": "product-services",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Additional services and choices",
    "paths": [
      "/admin/catalog/product-services"
    ],
    "paragraphs": [
      "Manage reusable services such as wrapping or printing, including priced choices and availability."
    ],
    "steps": [
      "Search or filter by status, then create or edit a service.",
      "Enter its name, code, choices, prices and statuses in the editor.",
      "Save and inspect the listed choices and linked-product count.",
      "Attach the service from a product package and services tab, marking selection required when needed."
    ],
    "fields": [
      "Service choices: customer alternatives with individual charges.",
      "Linked products: products using the service.",
      "Status: availability of the service or choice."
    ],
    "tips": [
      "Editing a shared service can affect multiple products. Charges apply per item."
    ],
    "examples": [
      "A wrapping service can be reused on two products; review the price per selected unit."
    ],
    "troubleshooting": [
      "A service is missing from a product: save, activate and bind it in the product’s service settings."
    ]
  },
  {
    "id": "reviews",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Product review moderation",
    "paths": [
      "/admin/catalog/reviews",
      "/admin/catalog/reviews/:id"
    ],
    "paragraphs": [
      "Review customer feedback and decide which reviews are visible in the store."
    ],
    "steps": [
      "Search and filter reviews, then open a record.",
      "Read its text, stars, customer, product and verified-purchase indicator.",
      "Approve, reject with an optional reason, or hide an approved review and inspect the outcome.",
      "Restore to approve a hidden review again; read the confirmation carefully before deleting."
    ],
    "fields": [
      "Rejection reason: optional explanation of the moderation decision.",
      "Helpful votes: customer reactions to the review.",
      "Approval and rejection: timestamps and actors where recorded."
    ],
    "tips": [
      "Hiding and rejection affect visibility. The delete action is permanent as its confirmation explains."
    ],
    "examples": [
      "Read review text, rating and product before approving or rejecting, then verify the saved status."
    ],
    "troubleshooting": [
      "A review is absent from the storefront: check moderation state, product and store before entering it again."
    ]
  },
  {
    "id": "catalog-excel",
    "group": "catalog",
    "group_title": "Catalog and products",
    "title": "Catalog Excel import and export",
    "paths": [
      "/admin/catalog/excel"
    ],
    "paragraphs": [
      "Transfer catalog data in bulk. The complete catalog page sends supported sheets together; an entity page sends only its own sheet."
    ],
    "steps": [
      "Download the template or export existing data to preserve correct columns and sheet names.",
      "Keep matching slug, code or SKU values and check catalog relationships.",
      "Upload from the appropriate screen, wait for results and inspect accepted rows and errors.",
      "Check sample records afterward, including names, prices, relationships and stock."
    ],
    "fields": [
      "Matching: uses slug, code or SKU according to the sheet.",
      "Blank cells: do not clear existing values during updates.",
      "Sheets beginning with _: examples excluded from import.",
      "Product export: all, active, or active low-stock products with five units or fewer."
    ],
    "tips": [
      "The limit is 20,000 rows. Records absent from a file are not deleted.",
      "Keep an export before large edits and avoid changing identifiers merely to rename records."
    ],
    "examples": [
      "Keep existing SKUs when updating prices and use three decimal places; do not change identity to rename products."
    ],
    "troubleshooting": [
      "A sheet was skipped: check its name, underscore prefix and upload screen, then inspect rejected rows."
    ]
  },
  {
    "id": "orders",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Orders list and filters",
    "paths": [
      "/admin/orders"
    ],
    "paragraphs": [
      "Review store orders with operational status, payment state, customer and total. Order status and successful payment are separate."
    ],
    "steps": [
      "Search by order or customer details and apply available status, payment, date, currency and source filters.",
      "Check total, currency and payment state before treating an order as collected.",
      "Open the order for items, address, payments, shipments and permitted edits.",
      "Use create order for the cashier screen."
    ],
    "fields": [
      "Order status: fulfillment, completion or cancellation stage.",
      "Payment status: recorded payment outcome including refunds.",
      "Date: order creation scope using the store reporting timezone."
    ],
    "tips": [
      "An order record alone is not proof of payment. Match dashboard dates and currencies when comparing counts."
    ],
    "examples": [
      "Check order number, customer, currency and payment status before editing or sending a document."
    ],
    "troubleshooting": [
      "Missing order: clear source, status, dates and search and verify the selected store."
    ]
  },
  {
    "id": "order-detail",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Order details, item editing and readiness",
    "paths": [
      "/admin/orders/:id"
    ],
    "paragraphs": [
      "Order details combine customer, address, items, totals, payments, shipments, activity, messages and documents."
    ],
    "steps": [
      "Check order summary, payment state, address and items before editing.",
      "Use available quantity, add-item and remove-item actions, then review recalculated totals.",
      "Mark individual items or all items ready. When all are ready, the order advances only if its current state allows it.",
      "Use the status action with any requested reason; invalid transitions are rejected.",
      "Inspect activity, payments and shipments to confirm each action."
    ],
    "fields": [
      "Item readiness: fulfillment readiness, not payment confirmation.",
      "Internal notes: visible to staff only.",
      "Messages: visible to the customer on the order page.",
      "Item removal: applies stock rules; inspect the confirmation and resulting totals.",
      "Pending: an initial order awaiting the next completion or review step.",
      "Confirmed: operational acceptance; inspect payment status independently.",
      "Processing: staff are preparing items.",
      "Out for delivery: the order is in the dispatch or delivery stage under its supported fulfillment flow.",
      "Shipped: the shipping-stage transition is recorded.",
      "Delivered: delivery to the customer is recorded.",
      "Cancelled: fulfillment stopped; inspect related financial and stock movements.",
      "Refunded: the order refund state; inspect payment and refund records for actual returned amounts."
    ],
    "tips": [
      "A gateway return message alone does not prove payment.",
      "Available edits depend on permissions and the current order stage."
    ],
    "examples": [
      "Mark items ready, then inspect the resulting order status and activity without assuming payment was confirmed."
    ],
    "troubleshooting": [
      "An action is absent: check its permission, current status and full refunds, not only order-view access."
    ]
  },
  {
    "id": "order-checks",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Order cycle: payment, confirmation, cancellation and refunds",
    "paths": [],
    "paragraphs": [
      "Read order and payment statuses together. Operational cancellation, financial refunds and stock returns have different effects and must be verified separately."
    ],
    "steps": [
      "Review the customer, total, currency, selected payment method and recorded payments.",
      "Read the unpaid-order warning before confirming; continue only when fulfillment is appropriate for the method and store policy.",
      "For electronic payments check approved confirmation evidence. For COD review the amount still to collect without recording cash that has not been received.",
      "After confirmation follow item readiness, driver, shipment and delivery through allowed actions; one action does not unlock every later transition.",
      "Before cancellation review fulfillment stage, reason, stock impact and payments.",
      "Use Payments or the order return workflow for refunds. Verify the refundable amount and final status, then review cashback and returned goods separately.",
      "Check activity, reconciliation and movements to verify completion. A fully refunded order is not resumed as a new sale by changing its status."
    ],
    "fields": [
      "Confirmation approves order fulfillment; it is not confirmation of electronic or cash collection.",
      "COD can carry a verification indicator while actual collection remains a separate step.",
      "A pending refund has not been confirmed successful; do not duplicate it because status updates are delayed.",
      "A stock return records inspected sellable quantity. Damaged and restocked quantities have different effects.",
      "Fully refunded: inspect both payment and order states and unavailable actions before attempting another transition."
    ],
    "tips": [
      "Keep payment or refund references and the rejection message for support. A delayed screen update is not a reason to create another financial transaction."
    ],
    "examples": [
      "Cancelling a paid electronic order requires checking its refund workflow; a Cancelled badge is not a refund receipt. A partial refund does not prove every product unit was restocked."
    ],
    "troubleshooting": [
      "Status update rejected: check allowed transitions, payment and refund states, fulfillment stage and the displayed reason.",
      "Payment succeeded but the order looks unexpected: inspect the linked payment and order and refresh before making a second sale."
    ]
  },
  {
    "id": "order-documents",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Order documents, tax invoices and ERP",
    "paths": [],
    "paragraphs": [
      "Use Documents and ERP invoice tabs to print order documents, issue tax invoices and review external invoice delivery."
    ],
    "steps": [
      "Open Documents to print or view the available order document.",
      "For a tax-enabled order and sufficient permission, issue a tax invoice after reading the financial snapshot confirmation.",
      "View or download its PDF; regenerate or void it with a reason where permitted.",
      "In ERP invoice, inspect the connection, reference and previous attempts before sending or retrying."
    ],
    "fields": [
      "Tax invoice: uses the order financial snapshot; tax-disabled orders cannot issue one here.",
      "Voiding: requires a reason and does not reuse the voided invoice number.",
      "ERP reference: an external reference, distinct from the local invoice number."
    ],
    "tips": [
      "Resending an already sent invoice requires specific confirmation.",
      "Later tax configuration changes do not rewrite previous order snapshots."
    ],
    "examples": [
      "Printing an order produces its document; issuing a tax invoice fixes its values in a separate workflow."
    ],
    "troubleshooting": [
      "An older invoice differs from current settings: inspect its saved snapshot and issue date before changing store settings."
    ]
  },
  {
    "id": "order-invoice-delivery",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Sending order invoices by email or WhatsApp and checking delivery",
    "paths": [],
    "paragraphs": [
      "Send an order invoice from its details using ready channels. The order invoice and attached PDF do not issue a tax invoice; tax invoice issuance is a separate action."
    ],
    "steps": [
      "Open the order and choose Send invoice when permitted. Review available channels and recipient email or phone before confirming.",
      "Choose email, WhatsApp or both ready channels, send once and wait for the attempt to be recorded.",
      "Email includes the invoice and a PDF attachment. WhatsApp includes a signed download link valid for 7 days from preparation for sending.",
      "Review recent invoice attempts in its dialog or open Notifications → Deliveries for statuses, failure reasons and retries.",
      "For automatic sending, check email settings and the order invoice event. Electronic payment requires confirmed collection; COD can receive an order invoice without claiming collection.",
      "Configure optional invoice BCC recipients in email notification settings, save and verify using an approved test recipient."
    ],
    "fields": [
      "Recipient uses valid saved order contact details, then customer details as a fallback. Review it before sending order information.",
      "Order invoice shows items, images, quantities, prices, discounts, shipping and payment status, with the store logo when available.",
      "PDF is attached to email and downloadable through the WhatsApp link.",
      "BCC adds hidden copies for configured store recipients without displaying their address list to the customer.",
      "Pending or queued means an attempt was accepted for processing, not that the message arrived.",
      "Automatic sending deduplicates the invoice event for an order. An intentional manual send is a separate attempt."
    ],
    "tips": [
      "Check sender settings, provider, event activation and background processing when delivery is delayed. A mail failure does not undo a confirmed payment.",
      "COD verification does not establish that cash has been collected. Read the actual collection amount and payment status."
    ],
    "examples": [
      "A confirmed electronic payment can queue an invoice when email and the event are enabled and an email address exists. A COD invoice may still show the amount as uncollected."
    ],
    "troubleshooting": [
      "Missing action: check invoice-sending permission. Unavailable channel: check provider readiness and a valid recipient email or phone.",
      "Failed attempt: inspect its reason, fix settings or recipient data, then use the available retry rather than repeatedly sending.",
      "Expired WhatsApp link: request an intentional new send after reviewing the recipient; do not edit the old signed URL."
    ]
  },
  {
    "id": "pos",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Cashier and manual order creation",
    "paths": [
      "/admin/orders/create"
    ],
    "paragraphs": [
      "Build a manual sale with customer, products, variants, delivery and payment allocation. Carts can be held and resumed."
    ],
    "steps": [
      "Find or create a customer, or use the cash customer where appropriate.",
      "Search names or SKUs, scan barcodes and choose variants before adding.",
      "Review quantities, discounts and unit prices. Price overrides require permission and a reason.",
      "Choose delivery with a saved or manual address, or pickup with an available branch.",
      "Allocate payment amounts, review remaining due and change, then create the order and wait for confirmation.",
      "Open order entry with the POS shortcut beside the top-bar language selector when a store is selected and orders.create is granted."
    ],
    "fields": [
      "Hold cart: saves a cashier cart; resuming can replace the current cart after confirmation.",
      "Payments: must satisfy the amount due and validation rules.",
      "Wallet: allocation cannot exceed available customer balance.",
      "Price override: separate from line discount; restore catalog price removes an override.",
      "Source and creator: an order created here records POS and the employee account for Order entry sales reporting."
    ],
    "tips": [
      "Use hold or complete the order before leaving an unsaved cart.",
      "Order creation is a real sale; review products, variants, address and branch first."
    ],
    "examples": [
      "A POS order records its creator in the entry report; staff with no orders appear with zero values."
    ],
    "troubleshooting": [
      "Missing shortcut: check selected store and order-create permission. Creation rejected: review fields, stock, shipping and payment amounts."
    ]
  },
  {
    "id": "customers",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Customers list",
    "paths": [
      "/admin/customers"
    ],
    "paragraphs": [
      "Find store customers and inspect their contact details, account state and available activity indicators."
    ],
    "steps": [
      "Search by name, email or phone and apply available filters.",
      "Check contact details to distinguish similar names.",
      "Open details for profile, addresses, orders and wallet information according to permission."
    ],
    "fields": [
      "Status: account enabled or disabled; deleted accounts can remain for review.",
      "Current device: latest recorded activity device in this store, not necessarily the signup device."
    ],
    "tips": [
      "Interpret store-specific customer orders in the currently selected store context."
    ],
    "examples": [
      "Distinguish customers with identical names by email, phone and customer ID before a financial action."
    ],
    "troubleshooting": [
      "Missing customer: check store context, store relationship, status filters and search."
    ]
  },
  {
    "id": "customer-detail",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Customer details, activation and verification",
    "paths": [
      "/admin/customers/:id"
    ],
    "paragraphs": [
      "Review profile, statistics, addresses, orders and wallet. Sensitive edits depend on permission and account state."
    ],
    "steps": [
      "Inspect identity, contact verification and recent device activity.",
      "Edit allowed fields, save the profile and wait for confirmation.",
      "Use activate or deactivate, read the impact and confirm with an optional reason.",
      "Review store statistics and addresses and open linked orders.",
      "Use wallet actions only with the appropriate financial permission.",
      "Use Log out all devices in the customer header when permitted to update customer status, verify the account in confirmation and check success."
    ],
    "fields": [
      "Email and phone verification: administrative flags requiring confirmed customer details.",
      "Deactivation: blocks sign-in and revokes current API tokens under the action rules.",
      "Permanently deleted account: retained for review and cannot be restored here.",
      "Customer logout revokes sessions without deleting the account, orders or wallet balance. Deleted accounts do not expose ordinary account-edit actions."
    ],
    "tips": [
      "Store spending statistics are separate from customer wallet balance."
    ],
    "examples": [
      "After changing customer status inspect activation and sessions; order count is not wallet balance."
    ],
    "troubleshooting": [
      "Logging out all devices does not prevent a new valid login; use account deactivation when that is the intended action."
    ]
  },
  {
    "id": "wallet",
    "group": "sales",
    "group_title": "Orders, customers and wallet",
    "title": "Wallet, cashback and balance transactions",
    "paths": [
      "/admin/wallet-transactions"
    ],
    "paragraphs": [
      "Review wallet movement in the transaction list. Authorized adjustments and cashback grants are available from customer details."
    ],
    "steps": [
      "Filter or search transactions and inspect type, amount, reference and customer.",
      "For an adjustment, open the customer wallet, choose credit, debit or cashback and complete required details.",
      "Check available and reserved balances, confirm, then inspect the new movement and balance.",
      "For an idempotency conflict, investigate the first attempt instead of blindly repeating the adjustment with another key.",
      "To reverse a specific cashback award, review customer cashback transactions and use the permitted reversal action, then inspect the resulting balance and movement."
    ],
    "fields": [
      "Balance and reserved: reserved money is not immediately available to spend.",
      "Cashback: credited to the general wallet, not a separate spendable balance.",
      "Store summary: distinguishes store rewards from general wallet totals where displayed."
    ],
    "tips": [
      "Order cashback is awarded after confirmed payment. Partial refunds or multiple awards may require manual review.",
      "Adjustments are real financial movements; verify customer, reason and amount first."
    ],
    "examples": [
      "A balance of 10.000 with 3.000 held does not mean all 10.000 is spendable; inspect available balance."
    ],
    "troubleshooting": [
      "Possible duplicate movement: inspect the reference and first result before another credit or debit."
    ]
  },
  {
    "id": "payments",
    "group": "finance",
    "group_title": "Payments and reconciliation",
    "title": "Payments, details and provider verification",
    "paths": [
      "/admin/payments",
      "/admin/payments/:id"
    ],
    "paragraphs": [
      "Inspect payment attempts, outcomes and refundable amounts, then open details for financial transactions and confirmation evidence."
    ],
    "steps": [
      "Search by payment, reference, order or customer and filter status, gateway, dates or refund presence.",
      "Open a payment and inspect attempted, paid, refunded and refundable amounts.",
      "For delayed gateway confirmation, use provider verification where supported and review the updated state.",
      "To refund, complete the amount and required reason after checking the refundable balance.",
      "Inspect the resulting refund record; submission is not immediate proof of completion."
    ],
    "fields": [
      "Gateway reference and transaction ID: match the provider operation.",
      "Provider status and last check: the latest recorded verification result.",
      "Refundable: remaining eligible amount after previous refunds."
    ],
    "tips": [
      "Browser return alone does not confirm payment; use provider evidence, webhooks or supported verification.",
      "Inspect existing refund records before retrying a slow request."
    ],
    "examples": [
      "Multiple attempts for one order do not establish multiple successful collections; check state, reference and amount."
    ],
    "troubleshooting": [
      "The provider confirms payment but the screen is pending: use supported verification and inspect webhook and reconciliation before another payment."
    ]
  },
  {
    "id": "refunds",
    "group": "finance",
    "group_title": "Payments and reconciliation",
    "title": "Refunds and money-return tracking",
    "paths": [
      "/admin/refunds",
      "/admin/refunds/:id"
    ],
    "paragraphs": [
      "This register tracks financial refunds, rather than inventory returns alone. Records link to payments and orders where available."
    ],
    "steps": [
      "Search by reason, reference or transaction and apply available filters.",
      "Open a refund to inspect amount, customer, payment, actor and processing timestamps.",
      "Use provider status verification when available and wait for the result.",
      "Open the original payment for remaining refundable value; create new refunds through payment or order actions."
    ],
    "fields": [
      "Status: the recorded provider or system refund processing state.",
      "Processed at: recorded processing time, distinct from creation time.",
      "Reason and reference: support later audit and investigation."
    ],
    "tips": [
      "Review cashback reconciliation notices when shown; some refund scenarios need separate reward review."
    ],
    "examples": [
      "A 2.000 refund from 10.000 does not cancel the entire order value; check remaining funds and refund state."
    ],
    "troubleshooting": [
      "Lower refundable balance: inspect earlier or pending refunds and provider limits."
    ]
  },
  {
    "id": "webhooks",
    "group": "finance",
    "group_title": "Payments and reconciliation",
    "title": "Payment webhook logs",
    "paths": [
      "/admin/payment-webhook-logs",
      "/admin/payment-webhook-logs/:id"
    ],
    "paragraphs": [
      "Inspect incoming gateway notifications and processing outcomes when investigating delayed confirmation or callback errors."
    ],
    "steps": [
      "Search by gateway or error and filter processed or unprocessed notifications.",
      "Open a record and inspect state, receipt time, processing time and safe payload summary.",
      "Match references to the payment and inspect its current state separately.",
      "For repeated errors, review the configured webhook URL or escalate references without sharing secrets."
    ],
    "fields": [
      "Processed: notification processing state, not necessarily a successful charge.",
      "Payload summary: limited safe information rather than full secret-bearing payloads."
    ],
    "tips": [
      "A webhook can describe failure, pending status or refund. Receipt alone does not prove collection."
    ],
    "examples": [
      "Inspect processing status and linked payment/order references, not just a browser notification."
    ],
    "troubleshooting": [
      "Rejected webhook: inspect the reason and provider signature/configuration with the administrator; do not manually trust an unverified event."
    ]
  },
  {
    "id": "reconciliation",
    "group": "finance",
    "group_title": "Payments and reconciliation",
    "title": "Financial reconciliation, scanning and resolution",
    "paths": [
      "/admin/reconciliation",
      "/admin/reconciliation/:id"
    ],
    "paragraphs": [
      "Find discrepancies between orders, payments and transactions, and document investigation and resolution."
    ],
    "steps": [
      "Run a scan after reading its confirmation and inspect the resulting issues.",
      "Use unresolved to include open and acknowledged issues, or filter a particular state, category or severity.",
      "Open an issue and inspect expected, actual, difference and recommended resolution.",
      "Acknowledge investigation. Use payment-flag synchronization only after reviewing payment truth.",
      "After correcting the cause, resolve with a code and note and inspect the new state."
    ],
    "fields": [
      "Acknowledge: records review without resolving the discrepancy.",
      "Expected and actual: the evidence behind the issue.",
      "Payment synchronization: aligns flags with recorded payment truth; it does not invent successful charges."
    ],
    "tips": [
      "Scanning updates issue records, not payment success by itself.",
      "Document actual corrective work rather than marking an unexplained difference resolved."
    ],
    "examples": [
      "Investigate mismatched payment and order states in their underlying records before marking the issue resolved."
    ],
    "troubleshooting": [
      "An issue returned after scanning: review the underlying cause; acknowledgement does not automatically fix source data."
    ]
  },
  {
    "id": "shipping",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipping setup from the beginning",
    "paths": [],
    "paragraphs": [
      "Shipping requires an enabled delivery country, available method and a rate matching the address and order conditions. A country reference alone does not enable delivery."
    ],
    "steps": [
      "Check Countries and create any missing reference, then enable it in Delivery countries.",
      "Create cities and areas where precise addressing or pricing is needed.",
      "Create a shipping method with its type, address requirement and cash-on-delivery support.",
      "Add country, city or area rates with conditions and status.",
      "Test ordinary and exception addresses and orders near free-shipping thresholds.",
      "For weight-priced delivery create a Zone plan and assign it to the delivery country. For Standard pricing configure country, city or area rates."
    ],
    "fields": [
      "Countries: shared country names and codes.",
      "Delivery countries: destinations enabled for this store.",
      "Scope: matching area rates take precedence over city, then country rates."
    ],
    "tips": [
      "For unexpected prices, inspect method, location, status, weight and order-value conditions together."
    ],
    "examples": [
      "Prepare delivery country, method and Standard or Zone pricing before expecting checkout to support a new destination."
    ],
    "troubleshooting": [
      "A visible country has no delivery quote: a reference country alone does not enable delivery or provide a matching rate."
    ]
  },
  {
    "id": "countries",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Countries: shared reference data",
    "paths": [
      "/admin/shipping/countries",
      "/admin/shipping/countries/create",
      "/admin/shipping/countries/:id/edit"
    ],
    "paragraphs": [
      "Manage country names, codes and reference details. This catalog is shared; delivery availability is assigned separately per store."
    ],
    "steps": [
      "Search first to avoid duplicate country references.",
      "Create or edit translated names, two-letter code, calling code, currency code, order and status.",
      "Save and assign the country through the selected store Delivery countries screen."
    ],
    "fields": [
      "Country code: examples include KW, EG and SA; it is not the calling code.",
      "Currency code: such as KWD, separate from store currency configuration.",
      "Status: inactive references may be absent from selectors."
    ],
    "tips": [
      "Consider all stores before editing shared data. Do not delete a country to fix a shipping-rate problem."
    ],
    "examples": [
      "KW identifies Kuwait while +965 is its calling code; use each field for its intended purpose."
    ],
    "troubleshooting": [
      "Country unavailable for delivery: check its reference status and enable it in the store’s Delivery countries."
    ]
  },
  {
    "id": "delivery-countries",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Delivery countries and order limits",
    "paths": [
      "/admin/shipping/delivery-countries",
      "/admin/shipping/delivery-countries/new",
      "/admin/shipping/delivery-countries/:id/edit"
    ],
    "paragraphs": [
      "Assign an existing country to the store, with availability, optional order thresholds and estimated delivery days."
    ],
    "steps": [
      "Check the selected store, add a delivery country and choose its reference.",
      "If missing, use the Countries link to create the reference and return.",
      "Set optional minimum order, free-shipping threshold, estimated days and status, then save.",
      "Configure matching shipping methods and rates and test an address in the country."
    ],
    "fields": [
      "Minimum order: required order value under shipping rules.",
      "Free-shipping threshold: an applicable threshold for free delivery.",
      "Estimated days: a range, separate from a booked delivery slot.",
      "Shipping plan selects Standard pricing or a Zone in this store. Changes to a shared plan affect linked countries."
    ],
    "tips": [
      "A saved assignment cannot change its country reference.",
      "Enabling a destination does not automatically create every shipping-method rate."
    ],
    "examples": [
      "Two countries can share one weight plan; changing that plan affects both."
    ],
    "troubleshooting": [
      "Country price did not change: inspect Standard versus Zone mode and edit the source actually in use."
    ]
  },
  {
    "id": "cities",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Cities",
    "paths": [
      "/admin/shipping/cities",
      "/admin/shipping/cities/create",
      "/admin/shipping/cities/:id/edit"
    ],
    "paragraphs": [
      "Create a city within a country for addresses and city-level shipping prices."
    ],
    "steps": [
      "Filter by country and search before creating a duplicate.",
      "Choose the country and enter translated names, code, order and status.",
      "Save, then use the city in areas or city-scoped rates."
    ],
    "fields": [
      "Country: determines the city parent used by addresses and pricing.",
      "Code: a city identifier, not a substitute for selecting the correct record."
    ],
    "tips": [
      "Similar city names in different countries are separate records; verify both country and name."
    ],
    "examples": [
      "A city in Kuwait belongs to a KW address, not another country with a similar city name."
    ],
    "troubleshooting": [
      "Empty city list: check country selection, activation and loading, then choose again."
    ]
  },
  {
    "id": "areas",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Areas",
    "paths": [
      "/admin/shipping/areas",
      "/admin/shipping/areas/create",
      "/admin/shipping/areas/:id/edit"
    ],
    "paragraphs": [
      "Areas belong to a city and country and support precise exceptions, such as three areas with a different rate."
    ],
    "steps": [
      "Choose country and city; create the city first if necessary.",
      "Enter translated names, code, order and status and save.",
      "Create an area-specific rate for the intended shipping method."
    ],
    "fields": [
      "Country and city: determine eligible area selections.",
      "Area: the most specific supported location scope for rates."
    ],
    "tips": [
      "Exception prices belong in Shipping rates, not in area or city names."
    ],
    "examples": [
      "An area-specific rate must use the correct parent city and country even when names repeat."
    ],
    "troubleshooting": [
      "Missing area: select the correct city first and verify the area’s status and relationship."
    ]
  },
  {
    "id": "shipping-methods",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipping methods, delivery and pickup",
    "paths": [
      "/admin/shipping/methods",
      "/admin/shipping/methods/new",
      "/admin/shipping/methods/:id/edit"
    ],
    "paragraphs": [
      "A method defines the customer service, such as local delivery or branch pickup. Detailed pricing uses rates or branch assignments."
    ],
    "steps": [
      "Create translated names and description, code, type, order and status.",
      "Set address requirement and cash-on-delivery support and save.",
      "For delivery, create matching country, city or area rates.",
      "For pickup, save the type first, then assign branches, optional prices and save branch assignments."
    ],
    "fields": [
      "Requires address: used by delivery methods needing a customer address.",
      "Cash on delivery support: method compatibility, separate from enabling its payment gateway.",
      "Active for method: branch assignment, separate from the branch own pickup availability."
    ],
    "tips": [
      "Inactive methods are hidden. Assigning a branch does not override its disabled pickup state."
    ],
    "examples": [
      "Pickup requires an enabled branch assigned to that method; a delivery address is not a substitute."
    ],
    "troubleshooting": [
      "A destination change left an old price: select a currently eligible quote for the new destination before completion."
    ]
  },
  {
    "id": "shipping-rates",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipping rates and country, city and area priority",
    "paths": [
      "/admin/shipping/rates",
      "/admin/shipping/rates/new",
      "/admin/shipping/rates/:id/edit"
    ],
    "paragraphs": [
      "Rates belong to a shipping method and country, optionally narrowed to a city or area. Matching area rates precede city rates, then country rates; sort order resolves equal specificity."
    ],
    "steps": [
      "Add a rate, choose method and country, and enter price and status.",
      "Leave city and area blank for a country rate; choose only city for a city rate, or city and area for an area rate.",
      "Set optional order-value, weight, free-shipping and estimated-day conditions and save.",
      "Example: Kuwait at 0.500 plus Kuwait City at 4.000 applies 4.000 for that city when its conditions match.",
      "For three exceptional areas, keep the general country rate and add three area-specific rules for the same method."
    ],
    "fields": [
      "Scope: derived from selected location records.",
      "Value and weight limits: can prevent a configured rule from matching.",
      "Free-shipping threshold: can make the final price zero when applicable.",
      "Sort order: lower values precede equal-specificity matching rules."
    ],
    "tips": [
      "If the general price appears, inspect address location IDs, method, status and conditions.",
      "Keep the actual general price and each exception in separate rules."
    ],
    "examples": [
      "An eligible area-specific rule takes priority over a country rule; also inspect total and weight conditions."
    ],
    "troubleshooting": [
      "Shipping is zero: inspect free-shipping thresholds, the rate and selected method before assuming a pricing error."
    ]
  },
  {
    "id": "shipping-zones",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipping Zone plans and the weight-price table",
    "paths": [
      "/admin/shipping/zones"
    ],
    "paragraphs": [
      "A Zone plan holds weight pricing that can be assigned to one or more delivery countries. Choose a full shipment price by weight range or a first-half-kilogram price plus incremental half-kilogram charges."
    ],
    "steps": [
      "Open Shipping → Zones and select the pricing type. Viewing prices and managing them require different permissions.",
      "For range pricing, add a named Zone column. Rows are weights in kilograms and cells are prices in the store currency.",
      "Enter increasing weights or generate them using a starting weight, increment and maximum. Review every price; weight rows can be edited, added or removed.",
      "Empty cells are only allowed after the last available weight, not between priced rows. Correct errors, save the table and wait for the result.",
      "For incremental pricing, enter the plan name, first 0.500 kg price, increasing band limits and the price per additional half kilogram within each band. Activate and save.",
      "Open Delivery countries, add or edit a country, select the saved shipping plan instead of Standard pricing and save.",
      "Check active shipping methods and product weights, then test several basket weights, especially at band limits and above the maximum."
    ],
    "fields": [
      "Range price is the full shipment price for the first limit covering the basket weight, not a per-kilogram charge or the sum of earlier rows.",
      "First half kilogram is the base incremental charge. A partial additional half kilogram is charged as a whole increment.",
      "Up to weight is a cumulative kilogram limit, not the band width. Limits must increase; an open final limit is allowed only in the last row.",
      "Additional half-kilogram price applies to increments inside that band.",
      "Custom weight rows allow up to three decimal places. Incremental band limits follow half-kilogram steps.",
      "Country shipping plan can be shared by multiple countries; price changes affect its linked countries.",
      "Standard pricing uses country, city and area rates instead of the weight plan."
    ],
    "tips": [
      "Basket weight follows product weights and quantities. Use kilograms consistently when entering or importing prices.",
      "Exceeding the last available weight can hide the method; a missing quote is not free shipping.",
      "Check minimum-order and free-shipping conditions too; they can make the final price zero."
    ],
    "examples": [
      "Ranges: up to 0.500 kg costs 3.780 and up to 1.000 kg costs 4.800 KWD. A 0.750 kg basket costs 4.800 in total.",
      "Incremental: first 0.500 kg costs 3.000 and each extra half kilogram up to 3.000 kg costs 1.000. A 1.200 kg basket costs 5.000 KWD."
    ],
    "troubleshooting": [
      "A plan does not affect the country: check the saved assignment and whether both the country and plan are active.",
      "Unexpected boundary price: inspect product weights, quantities and pricing type; do not enter grams in a kilogram field.",
      "The table will not save: fix duplicate or unordered weights and gaps between priced rows, then read the field errors before leaving."
    ]
  },
  {
    "id": "delivery-slots",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Delivery slots, weekdays and capacity",
    "paths": [
      "/admin/shipping/delivery-slots"
    ],
    "paragraphs": [
      "Configure delivery windows such as 09:00–12:00 with weekdays and optional capacity."
    ],
    "steps": [
      "Review existing windows before adding overlapping or duplicate entries.",
      "Enter name, start and end time and at least one weekday.",
      "Set capacity, order and status, save and inspect the refreshed list.",
      "Edit through the row action, toggle availability or read the delete confirmation."
    ],
    "fields": [
      "Weekdays: days on which the window operates.",
      "Capacity: the booking limit used by scheduling; blank means no recorded limit.",
      "Start and end: time window, separate from estimated delivery days."
    ],
    "tips": [
      "End time must follow start time and weekdays must be valid. Inspect field errors on rejection.",
      "Kalemat hides an empty delivery date/time selector when no enabled slots exist. Slots are separate from a shipping method’s estimated delivery text."
    ],
    "examples": [
      "A 09:00–12:00 slot has operating days and capacity; delivery in 2–4 days is a separate estimate."
    ],
    "troubleshooting": [
      "Slot unavailable: inspect activation, weekday, capacity, date and fulfillment method."
    ]
  },
  {
    "id": "branches",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Branches, pickup and business hours",
    "paths": [
      "/admin/shipping/branches",
      "/admin/shipping/branches/new",
      "/admin/shipping/branches/:id/edit"
    ],
    "paragraphs": [
      "Branches support pickup, contact-page details, maps and business hours according to enabled options."
    ],
    "steps": [
      "Enter translated names, code, contacts, addresses and descriptions.",
      "Set map URL or coordinates, pickup, contact visibility, main-branch flag, status and order.",
      "Save first, then edit to configure weekly business hours.",
      "Assign the branch to pickup methods and manage its contact channels separately."
    ],
    "fields": [
      "Pickup enabled: allows use through assigned pickup methods.",
      "Contact visibility: works together with contact-page display settings.",
      "Business hours: weekly opening schedule, separate from order delivery slots."
    ],
    "tips": [
      "Creating a branch does not assign it to every pickup method."
    ],
    "examples": [
      "A branch shown on Contact is not a pickup location until pickup is enabled and the method is assigned."
    ],
    "troubleshooting": [
      "Missing pickup branch: check branch, method, assignment and activation, not just its name."
    ]
  },
  {
    "id": "carriers",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipping carriers",
    "paths": [
      "/admin/shipping/carriers",
      "/admin/shipping/carriers/new",
      "/admin/shipping/carriers/:id/edit"
    ],
    "paragraphs": [
      "Define shipment carriers. The configuration form currently supports the manual driver."
    ],
    "steps": [
      "Find or create a carrier with name, code and available driver.",
      "Enter a webhook secret only when required by an approved integration, set status and save.",
      "Choose the carrier when creating an order shipment and record tracking details."
    ],
    "fields": [
      "Code: the internal carrier identifier.",
      "Manual driver: shipment and tracking details follow staff procedures.",
      "Configured secret: indicates presence without exposing the value."
    ],
    "tips": [
      "A carrier name alone does not create an automated provider connection or purchase a shipping label."
    ],
    "examples": [
      "Configure the carrier, select it when creating a shipment and record the correct tracking reference."
    ],
    "troubleshooting": [
      "Tracking fails: check carrier, URL and reference; manually saving a number does not prove carrier registration."
    ]
  },
  {
    "id": "shipping-drivers",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Delivery drivers and assigning a driver to an order",
    "paths": [
      "/admin/shipping/drivers"
    ],
    "paragraphs": [
      "Maintain this store’s driver list, then assign a driver from a delivery order. Creating a driver record does not automatically create a login account."
    ],
    "steps": [
      "Open Shipping → Delivery drivers. Search by name or phone and check the active filter before creating a duplicate.",
      "Add the name, phone, notes and active status, save and check the new record.",
      "Open an editable delivery order, choose an active driver in its driver card and save the assignment.",
      "To change or clear the assignment, select another driver or No driver, save and verify the order details.",
      "Deactivate a driver to stop new assignments; review previously assigned orders separately."
    ],
    "fields": [
      "Name is displayed in the selector and order.",
      "Phone must be valid with its country code and unique within the store.",
      "Active allows new assignment. A previous driver’s details may remain on historical orders.",
      "Notes are internal operating information, not a message sent to the driver.",
      "Permissions: shipping.drivers.view to view and shipping.drivers.manage to manage drivers; assignment requires shipping or shipment management access and access to the order."
    ],
    "tips": [
      "Assignment is unavailable for pickup, delivered, cancelled or refunded orders and fully refunded payments.",
      "Saving an assignment does not update shipment status, record collection or automatically notify the driver."
    ],
    "examples": [
      "Create an active driver and assign them to a delivery order in preparation. Delivery and collection are still recorded through their own actions."
    ],
    "troubleshooting": [
      "Driver missing from the selector: check the selected store and active status.",
      "Assignment is locked: check fulfillment type, order and payment statuses and the driver assignment permission."
    ]
  },
  {
    "id": "shipments",
    "group": "shipping",
    "group_title": "Shipping and delivery",
    "title": "Shipments, creation and tracking",
    "paths": [
      "/admin/shipping/shipments",
      "/admin/shipping/shipments/:id"
    ],
    "paragraphs": [
      "Inspect transport, tracking and status. Create shipments from an eligible confirmed order Shipment tab."
    ],
    "steps": [
      "Open a confirmed order, create a shipment and choose a carrier or available manual handling.",
      "Review copied recipient details and enter required tracking or weight information.",
      "Open shipment details from the list to update tracking and inspect its timeline.",
      "Choose the correct state, note and any cash-collection verification, then inspect the resulting order state.",
      "Read cancellation confirmation and distinguish shipment cancellation from order cancellation."
    ],
    "fields": [
      "Tracking number and URL: carrier tracking details.",
      "Cash on delivery: collection amount; verify collection only after actual confirmation.",
      "Timeline: recorded shipment events."
    ],
    "tips": [
      "Shipment state changes can advance the order automatically. Branch pickup does not use carrier shipments in the same way."
    ],
    "examples": [
      "Shipment, driver assignment and collection require their respective order actions."
    ],
    "troubleshooting": [
      "Shipment creation rejected: review order eligibility, confirmation, carrier, permission and the stated error."
    ]
  },
  {
    "id": "catalog-campaign",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Temporary product campaign: before and after prices",
    "paths": [],
    "paragraphs": [
      "Apply a dated price reduction to selected products and their variants. Normal prices return after the end without editing every product."
    ],
    "steps": [
      "Filter Products by department, category, brand or attribute value and select rows or all matching results.",
      "Change filters and append results to combine another group, then review the selection count.",
      "Choose temporary campaign and enter its name, discount type, value, start and end.",
      "Preview the count and first ten sample products, before/after prices and variant counts. Any field change requires a fresh preview.",
      "Save after review and manage the campaign from Promotions."
    ],
    "fields": [
      "Percentage: greater than zero and no more than 100; 20 percent off 75.500 gives 60.400.",
      "Fixed amount: deducted per eligible unit, with a zero price floor.",
      "Dates: entered in the browser timezone shown in the dialog and submitted as specific instants.",
      "Selection: at most 20,000 products; preview is only a sample."
    ],
    "tips": [
      "The product set is fixed at save time, includes variants and excludes service add-on charges.",
      "Overlapping catalog campaigns do not stack: one highest-priority campaign applies. Review any other cart promotions separately.",
      "Price eligibility follows request time. Existing scheduled expiry updates campaign state; each campaign needs no new cron entry."
    ],
    "examples": [
      "A temporary catalog campaign returns to normal pricing after its period without rewriting the original price."
    ],
    "troubleshooting": [
      "Unexpected preview count: review selection, filters and variants before applying the campaign."
    ]
  },
  {
    "id": "marketing",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Current and previous promotions and details",
    "paths": [
      "/admin/promotions",
      "/admin/promotions/:id"
    ],
    "paragraphs": [
      "All promotions, including product-created price campaigns, are kept here. Expiry does not delete their configuration or usage history."
    ],
    "steps": [
      "Open Promotions, leave status on all and search by name or coupon.",
      "Read schedule: active for running, scheduled for upcoming, expired after end and inactive for disabled offers.",
      "Inspect discount and dates; use the eye for details or chart action for usage.",
      "Edit type, discount, dates and eligibility through the pencil, or read confirmation before deactivating.",
      "Choose deleted-only records and restore where permitted."
    ],
    "fields": [
      "Status and schedule: administrative activation is separate from the valid time window.",
      "Priority: application order under promotion rules, including overlapping catalog campaigns.",
      "Eligibility: product, category, brand, shipping or country selections according to type."
    ],
    "tips": [
      "Reactivation does not extend an expired end date; edit dates when a new valid period is intended.",
      "Deletion is soft with restoration available. Deactivation retains configuration and history."
    ],
    "examples": [
      "An activated offer that ended yesterday remains saved but expired; activation alone does not extend it."
    ],
    "troubleshooting": [
      "An offer does not apply: review activation, dates, eligibility, priority, coupon and usage limits before editing a product price."
    ]
  },
  {
    "id": "promotion-form",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Create or edit a promotion or coupon",
    "paths": [
      "/admin/promotions/new",
      "/admin/promotions/create",
      "/admin/promotions/:id/edit"
    ],
    "paragraphs": [
      "Use the promotion form for cart rules, coupons, cashback and supported offer types. Fields and eligibility depend on the type."
    ],
    "steps": [
      "Enter translated names and descriptions and select the type.",
      "Set discount type, value, cap and priority where available.",
      "For a coupon, enter its code, require-coupon flag and public-listing option where appropriate.",
      "Set eligibility, order thresholds, overall and per-customer usage limits and dates.",
      "Review activation, flash-sale and stop-further settings, save and test eligible and ineligible carts."
    ],
    "fields": [
      "Eligibility: empty selections have type-dependent meaning; inspect active fields and rule summary.",
      "Usage limits: blank means unlimited where indicated, rather than zero uses.",
      "Stop further promotions: affects later rule application under the promotion engine.",
      "Dates: use the browser timezone when editing."
    ],
    "tips": [
      "Catalog price campaigns must remain product discounts without coupons, order-total conditions or usage limits.",
      "A regular cart promotion does not necessarily produce a crossed-out product-card price; use temporary product campaigns for that purpose."
    ],
    "examples": [
      "A 10% coupon capped at 2.000 differs from a fixed 10.000 discount; review the rule summary."
    ],
    "troubleshooting": [
      "Conditions rejected: they may not be compatible with the selected promotion type; do not change type merely to suppress an error."
    ]
  },
  {
    "id": "buy-x-get-y",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Buy X get Y promotion",
    "paths": [],
    "paragraphs": [
      "Define a qualifying purchase quantity and discounted reward units, then inspect the rule summary before enabling."
    ],
    "steps": [
      "Choose buy X get Y and set purchase eligibility and quantity X.",
      "Set reward quantity Y and its discount; 100 percent makes reward units free.",
      "Choose different reward products or leave empty to use cheapest eligible units from the purchase scope.",
      "Set repetition and reward caps, save and test different quantities."
    ],
    "fields": [
      "Pooled quantity: a mix of eligible items can satisfy X under the rule.",
      "Different reward product: the customer must add it; automatic gift insertion is unsupported.",
      "Cheapest units: chosen according to prices after preceding item discounts."
    ],
    "tips": [
      "Do not advertise automatic gift insertion. Test a cart containing both qualifying and reward items."
    ],
    "examples": [
      "Buy 2 get 1 free needs the correct basket quantity; inspect group repetition and reward limits."
    ],
    "troubleshooting": [
      "A separate reward was not automatically added: the customer must add that eligible reward product to the basket."
    ]
  },
  {
    "id": "promotion-usages",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Promotion usage and results",
    "paths": [
      "/admin/promotions/usages",
      "/admin/promotions/:promotionId/usage"
    ],
    "paragraphs": [
      "Inspect recorded uses with customer and order links, discount or cashback values and timestamps."
    ],
    "steps": [
      "Open all usages or the chart action on one promotion for its records only.",
      "Filter by promotion, customer or order, or search coupon code where available.",
      "Open related orders to inspect the applied discount."
    ],
    "fields": [
      "Discount: recorded reduction for the usage.",
      "Cashback or reward: the amount recorded according to promotion type.",
      "Usage time: recorded redemption, not a product impression."
    ],
    "tips": [
      "Usage counts do not measure campaign views. Use orders and financial reports when evaluating collections."
    ],
    "examples": [
      "A coupon usage links promotion, customer and order; open the named record rather than guessing from an ID."
    ],
    "troubleshooting": [
      "No usages despite activation: enabling a promotion is not a redemption; check order completion, usage rules and filters."
    ]
  },
  {
    "id": "abandoned-carts",
    "group": "marketing",
    "group_title": "Promotions and discounts",
    "title": "Abandoned carts and activity filters",
    "paths": [
      "/admin/promotions/abandoned-carts",
      "/admin/promotions/abandoned-carts/:id"
    ],
    "paragraphs": [
      "Shows server-saved carts containing items that have not become orders. Active and abandoned carts are available; closing the app alone does not change a cart to Abandoned."
    ],
    "steps": [
      "Check the selected store. Defaults are Customers only, Open and at least one day of inactivity.",
      "For a cart added half an hour ago, choose Any activity and keep Open (active + abandoned).",
      "For a guest cart choose Guests only or Customers and guests; Customers only excludes guest sessions.",
      "Search by customer contact or cart ID and review activity time, amount and currency before opening details.",
      "Review products, variants, quantities and contact details, then create a coupon or open notification templates if appropriate.",
      "To actually send a message, use Send message, review recipient, channel and content, then monitor Deliveries."
    ],
    "fields": [
      "Audience: customers have an account-linked cart; a guest cart belongs to a session and may have no contact details.",
      "Open includes Active and Abandoned. Selecting Abandoned alone excludes carts still marked Active.",
      "One day inactive means at least 24 hours since the saved cart update, not carts created today.",
      "Any activity removes the one-day wait while keeping the other filters.",
      "Last activity is the saved update time, not confirmation that the app was closed.",
      "Cart ID differs from order ID. Empty and converted carts are excluded.",
      "Creating a coupon does not automatically send it."
    ],
    "tips": [
      "Do not manually change cart status simply to make it visible; inspect audience, status and duration filters first.",
      "The app must save additions through the API. If the correct-store cart is missing under Any activity, verify the cart-add request, customer session and store scope.",
      "A cart is not a stock reservation or paid sale. Check availability and prices before outreach."
    ],
    "examples": [
      "A signed-in customer adds an item and closes the app half an hour later: the one-day inactivity filter hides it. Any activity can show it if it is saved with items in the selected store."
    ],
    "troubleshooting": [
      "Recent cart missing: choose the appropriate audience → Open → Any activity, clear search and check store and pagination.",
      "Still missing: investigate customer ID, store, addition time and the API request. A device-only cart cannot be displayed by the control panel.",
      "No email or phone: it may be a guest session; do not assign it to another account based on similar items."
    ]
  },
  {
    "id": "media",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Media library, folders and asset usage",
    "paths": [
      "/admin/media"
    ],
    "paragraphs": [
      "Manage reusable store assets and inspect recorded usage before deleting files linked to content."
    ],
    "steps": [
      "Choose all assets or a folder and search file names or available filters.",
      "Create a folder or upload and wait for completion and preview.",
      "Open an asset to inspect metadata and usage or copy its URL, then select it in the target screen media picker.",
      "Inspect usage before deleting; resolve linked content first if deletion is blocked."
    ],
    "fields": [
      "Folder: library organization.",
      "Usage: recorded content links relying on the asset.",
      "Copy URL: copies an address rather than attaching the file to a product."
    ],
    "tips": [
      "Uploading alone does not publish an asset in a banner or product."
    ],
    "examples": [
      "Upload an image or PDF into the intended folder and select it through a supported usage screen."
    ],
    "troubleshooting": [
      "File rejected: check actual type, size and field error; renaming the extension does not change the file type."
    ]
  },
  {
    "id": "banners",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Banners, mobile images and scheduling",
    "paths": [
      "/admin/content/banners",
      "/admin/content/banners/new",
      "/admin/content/banners/create",
      "/admin/content/banners/:id/edit"
    ],
    "paragraphs": [
      "Manage campaign imagery, translated headings, links, placements and optional schedules."
    ],
    "steps": [
      "Search the list and filter placement or status.",
      "Create translated title and subtitle, upload or choose an image and inspect its preview.",
      "Set an optional mobile image, destination, link type, placement and order.",
      "Set dates and status, add JSON only when required and understood, then save."
    ],
    "fields": [
      "Placement: supported storefront slots such as hero, secondary or category.",
      "Destination: the customer click target; test it after publication.",
      "Mobile image: an optional small-screen alternative where supported."
    ],
    "tips": [
      "Inspect image errors and previews. Soft deletion hides a banner; activation does not override its schedule or unsupported placement."
    ],
    "examples": [
      "An enabled banner scheduled for next week is not live today; also inspect its mobile image."
    ],
    "troubleshooting": [
      "Missing banner: inspect placement, schedule, activation, store, target link and device image."
    ]
  },
  {
    "id": "collections",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Product display collections",
    "paths": [
      "/admin/content/collections",
      "/admin/content/collections/new",
      "/admin/content/collections/create",
      "/admin/content/collections/:id/edit"
    ],
    "paragraphs": [
      "A collection is a product row for Home or Cart. Products can be selected manually or loaded automatically using catalog filters. Creating a collection does not create a discount."
    ],
    "steps": [
      "Enter translated name, identifier, placement, product limit, display order and active status.",
      "Choose automatic filter-based selection or manual selection of specific store products.",
      "In automatic mode set search, department, category, brand, featured, bestseller and in-stock conditions as needed.",
      "In manual mode search for and select products, then verify saved choices after reopening.",
      "Review sorting and limit, save and check the intended storefront placement."
    ],
    "fields": [
      "Automatic selection changes as products meet or leave its filters; it is not a frozen list.",
      "Manual selection restricts results to chosen products; check sorting rather than assuming selection-click order.",
      "Placement is Home or Cart according to storefront support.",
      "Limit and display order control product count and placement priority.",
      "Identifier is the collection identity used by the storefront."
    ],
    "tips": [
      "Collections do not change prices. Check product activation, stock conditions, filters and the limit if a selected product is missing."
    ],
    "examples": [
      "A five-product manual selection stays restricted to your choices; an automatic latest-products collection changes when new products meet its filters."
    ],
    "troubleshooting": [
      "Missing items: reopen the same collection and check selection mode, products or filters, sort, limit and product status, then refresh the storefront."
    ]
  },
  {
    "id": "pages",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Content pages and policies",
    "paths": [
      "/admin/content/pages",
      "/admin/content/pages/new",
      "/admin/content/pages/create",
      "/admin/content/pages/:id/edit"
    ],
    "paragraphs": [
      "Create translated information such as About us or return policies using the available page fields."
    ],
    "steps": [
      "Search for an existing page before duplicating it.",
      "Create or edit title, slug, translated content and available SEO, status and order fields.",
      "Review formatting and links, save and wait for confirmation.",
      "Open the storefront page to verify its content and route under the current theme.",
      "To change Kalemat’s two top-bar messages, edit top-bar-text, enter two paragraphs per language, activate and publish the page, save and check the storefront."
    ],
    "fields": [
      "Slug: the page identifier within supported content routes.",
      "Content: entered separately for each language.",
      "Status: controls availability according to storefront implementation.",
      "Publication time: the recorded publish field, reviewed together with status.",
      "Excerpt: a translated summary separate from full content.",
      "Kalemat top-bar text uses a published page identified as top-bar-text. The first two nonempty paragraphs of each language form the two texts; the page title is an administrative label."
    ],
    "tips": [
      "Creating a page does not necessarily add it to every storefront menu."
    ],
    "examples": [
      "A published two-paragraph top-bar-text page provides Kalemat’s top bar; Returns policy is a separate page."
    ],
    "troubleshooting": [
      "Missing content: check identifier, activation, publication time, language and storefront linkage, then refresh."
    ]
  },
  {
    "id": "quiz",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Quiz questions",
    "paths": [
      "/admin/content/quiz",
      "/admin/content/quiz/new",
      "/admin/content/quiz/create",
      "/admin/content/quiz/:id/edit"
    ],
    "paragraphs": [
      "Manage quiz questions, choices and order for storefront experiences that support the quiz."
    ],
    "steps": [
      "Inspect the existing question order and create or edit a question.",
      "Enter translated text, choices and the fields required by its type.",
      "Add translated answer labels, optional media and colors, attach answer products and inspect answer status and order.",
      "Set order and status, save and review choices in the list and supported storefront."
    ],
    "fields": [
      "Question: customer-facing text in the selected language.",
      "Choices: available answers and their editor data.",
      "Order and status: sequence and availability under the storefront experience.",
      "Selection mode: single or multiple choices according to the selected type.",
      "Question and answer keys: matching identifiers, separate from visible wording.",
      "Answer image, emoji and colors: choice presentation; inspect the preview.",
      "Answer products: products linked to that choice under the quiz experience."
    ],
    "tips": [
      "Not every storefront necessarily exposes the same quiz flow."
    ],
    "examples": [
      "Add the question and translated choices, then review order and activation in the supported quiz flow."
    ],
    "troubleshooting": [
      "Question missing: inspect activation, ordering, language and storefront quiz usage."
    ]
  },
  {
    "id": "contact-settings",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Contact page and message form settings",
    "paths": [
      "/admin/contact/settings"
    ],
    "paragraphs": [
      "Configure translated contact text, form, branches, map and business hours with an in-panel preview."
    ],
    "steps": [
      "Enter translated title and description and enable the page as required.",
      "Enable the form, set recipient email and translated privacy text.",
      "Choose the default branch and branch, map and hours visibility.",
      "Review preview and readiness, save and test the storefront form."
    ],
    "fields": [
      "Recipient email: follow-up destination according to delivery configuration.",
      "Default branch: primary location details when displayed.",
      "Form visibility: separate from telephone and social contact links."
    ],
    "tips": [
      "Contact channels and sending providers are configured separately. A preview is not a sent message."
    ],
    "examples": [
      "Enabling a Contact form differs from configuring email delivery or WhatsApp OTP."
    ],
    "troubleshooting": [
      "Contact form absent: check page settings and storefront support, then inspect the incoming messages screen."
    ]
  },
  {
    "id": "contact-channels",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Contact links and branch channels",
    "paths": [
      "/admin/contact/channels"
    ],
    "paragraphs": [
      "Manage telephone, email and social links shown on the contact page, footer or branch."
    ],
    "steps": [
      "Find a channel and create or edit it.",
      "Choose type, label, value, optional branch, primary flag, placements and status.",
      "Save and move channels up or down to order them.",
      "Test customer-facing links and read confirmation before deleting."
    ],
    "fields": [
      "Value: phone, email or URL matching the channel type.",
      "Placements: contact page, footer or branch where supported.",
      "Primary: identifies a main channel within supported presentation."
    ],
    "tips": [
      "A social contact link does not configure a WhatsApp or email sending provider; use notification channels for delivery."
    ],
    "examples": [
      "A Contact WhatsApp link opens a conversation; it does not configure the notification provider."
    ],
    "troubleshooting": [
      "Broken contact link: inspect type, value, activation and branch details, then test it on the storefront."
    ]
  },
  {
    "id": "contact-messages",
    "group": "content",
    "group_title": "Content and contact",
    "title": "Incoming contact messages",
    "paths": [
      "/admin/contact/messages"
    ],
    "paragraphs": [
      "Review contact-form submissions, new-message counts, search and follow-up state."
    ],
    "steps": [
      "Inspect new messages and filter or search name, email, subject and available dates.",
      "Open a message and read its content and contact details.",
      "Update its follow-up state using the available action and inspect the result.",
      "Reply through the approved customer channel when needed; changing state does not send a reply automatically."
    ],
    "fields": [
      "Status: internal follow-up stage.",
      "Sender details: submitted contact data requiring review before reuse."
    ],
    "tips": [
      "An empty list can reflect filters or a disabled form; inspect contact settings before assuming delivery failed."
    ],
    "examples": [
      "Open the message, review sender, subject and state and record follow-up using available actions."
    ],
    "troubleshooting": [
      "Missing message: check store, filters and actual form submission, not only email settings."
    ]
  },
  {
    "id": "operations",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Integrations, connection and synchronization",
    "paths": [
      "/admin/integrations",
      "/admin/integrations/:id"
    ],
    "paragraphs": [
      "Connect the store to systems such as Odoo or Focus. Connection setup, field mapping and synchronization are separate steps."
    ],
    "steps": [
      "Open an integration and inspect enabled state, test mode and last connection.",
      "Enter provider connection details; use the indicated Focus API root or Odoo database and username.",
      "Enter secrets only when replacing them; blank preserves saved values. Save and test the connection.",
      "Review product, stock, order directions and automatic sync options and save changes.",
      "Run stock sync from its action and product/category sync from field mapping, then inspect logs and queue health."
    ],
    "fields": [
      "Test mode: provider-specific test behavior, not proof of live readiness.",
      "Automatic sync: scheduled background configuration, separate from enabling a mapped entity.",
      "Secrets: stored values are hidden; blank inputs do not imply missing credentials."
    ],
    "tips": [
      "Connection success does not validate every mapping or sync. Test a sample and inspect logs.",
      "Use the provider actions actually supported by its configuration screen."
    ],
    "examples": [
      "A successful connection test precedes a sample sync preview; neither proves an order was sent."
    ],
    "troubleshooting": [
      "No automatic sync: inspect activation, schedule, worker and latest log before repeatedly starting manual work."
    ]
  },
  {
    "id": "integration-field-mapping",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Odoo field mapping and dry runs",
    "paths": [],
    "paragraphs": [
      "Inside Odoo configuration, map customers, departments and products, enable each entity and inspect samples before synchronization."
    ],
    "steps": [
      "Open Odoo field mapping and choose an entity.",
      "Review local/source fields and matching keys and save mappings.",
      "Enable the entity and run Dry Run to inspect samples and warnings before actual sync.",
      "Correct issues, run Sync Now and follow execution logs."
    ],
    "fields": [
      "Dry Run: preview validation before real synchronization.",
      "Sync Now: starts supported synchronization, potentially through the queue.",
      "Entity enabled: allows its mapping, separate from automatic schedule configuration."
    ],
    "tips": [
      "Imports can change real catalog records. Review source, matching rules and sample output first."
    ],
    "examples": [
      "Map the appropriate product identity and review Dry Run before a large import."
    ],
    "troubleshooting": [
      "Product duplicated after sync: inspect matching keys and mappings before deleting order-linked records."
    ]
  },
  {
    "id": "integration-payment-settings",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Odoo payment terms, gateway journals, discount and shipping mapping",
    "paths": [],
    "paragraphs": [
      "Integrations → Odoo → Configuration holds payment terms, gateway journals and shipping or discount products when supported. These external mappings do not change storefront payment methods or their collection rules."
    ],
    "steps": [
      "Save and test the Odoo connection before loading external choices.",
      "Open Payment terms and payment gateway mapping and load options from Odoo.",
      "Select the payment terms and journal for each gateway, verify external record names and save.",
      "Review the shipping and discount products if the integration uses separate lines for them.",
      "Review an appropriate order’s external reference and sync log to verify payment, shipping and discount mapping.",
      "If the payment method changes later, inspect the update to the same external order rather than expecting a new order."
    ],
    "fields": [
      "Payment terms map to payment_term_id, not the delivery time window.",
      "Payment journal maps to payment_journal_id when supported by the Odoo installation.",
      "Unmapped gateway uses the behavior shown in configuration; a gateway name alone does not establish the external journal.",
      "Discount line uses the configured external product for a separate order discount.",
      "Order reference links the store order to the external sales order for updates and retries."
    ],
    "tips": [
      "Loading choices reads Odoo data; saving configures mapping. Sending or resending an order is a separate action that requires reviewing the previous result."
    ],
    "examples": [
      "Map MyFatoorah to its intended journal and save. Review an order using that gateway in Odoo and verify the journal, payment terms and total."
    ],
    "troubleshooting": [
      "Choices will not load: check the connection, Odoo user permissions and supported fields.",
      "Missing shipping or discount line: inspect its configured external product, the order value and sync log before adding a possible duplicate manually."
    ]
  },
  {
    "id": "integration-bundle-orders",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Syncing orders and bundles to Odoo and investigating Quotations",
    "paths": [],
    "paragraphs": [
      "A store order keeps its external sales-order reference. Bundle export uses a priced parent line plus zero-priced component lines that describe contents without counting the sale twice."
    ],
    "steps": [
      "Review external mappings for the bundle, its components and variants, including each component quantity per bundle.",
      "Open the bundle order and review its saved items and total before ERP sending.",
      "After sending, check the reference, sync result and external order state rather than relying on the external number alone.",
      "If the result remains a Quotation, inspect its confirmation error, mappings, stock and Odoo configuration before retrying.",
      "For an already linked order, review the same reference and ensure another external order has not been created, especially before manual external changes."
    ],
    "fields": [
      "Bundle line holds the sold bundle quantity and order price.",
      "Component quantity is its per-bundle quantity multiplied by the number of bundles. Exported zero prices do not change component catalog prices.",
      "Shipping and discount use their configured separate lines; do not add prices to component lines to allocate them.",
      "Quotation is an external draft or offer, different from a confirmed sales order.",
      "Confirmed or completed orders should not have their lines rebuilt simply because sending was repeated."
    ],
    "tips": [
      "External product type and stock handling must avoid deducting both parent and component stock for the same sale. Inspect Odoo stock movements when product configuration is unsuitable."
    ],
    "examples": [
      "Two 9.000 KWD bundles each containing two A and one B export a parent quantity of 2 totaling 18.000, A quantity 4 at zero and B quantity 2 at zero, plus the order’s shipping and discount."
    ],
    "troubleshooting": [
      "Odoo total is too high: check duplicate component prices, tax, shipping and discount lines.",
      "Contents differ from today’s catalog: orders use the saved bundle snapshot; later catalog edits do not rewrite previous sales.",
      "Confirmation failure: creation of a Quotation is not completion of the full sending cycle. Review its reference and actual rejection reason."
    ]
  },
  {
    "id": "integration-mappings",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Integration record mappings",
    "paths": [
      "/admin/integrations/mappings"
    ],
    "paragraphs": [
      "Inspect links between local entities and external records to identify the target of synchronization."
    ],
    "steps": [
      "Choose integration, entity or available filters.",
      "Review local ID, external ID, direction and latest sync time.",
      "Investigate unexpected imports against source records, field mappings and sync logs."
    ],
    "fields": [
      "Local and external: identifiers of linked records.",
      "Direction: recorded mapping or sync direction.",
      "Last sync: latest recorded link synchronization."
    ],
    "tips": [
      "Record mappings differ from Odoo field-name mappings."
    ],
    "examples": [
      "A local product ID must map to the intended Odoo product; matching names are not enough."
    ],
    "troubleshooting": [
      "An update targets the wrong record: check entity type, both identifiers, direction and store."
    ]
  },
  {
    "id": "integration-logs",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Synchronization logs and retries",
    "paths": [
      "/admin/integrations/sync-logs"
    ],
    "paragraphs": [
      "Review connection and sync attempts, states, entities and timings with secret-redacted diagnostics."
    ],
    "steps": [
      "Filter integration, action or state and locate the intended attempt.",
      "Open its data for error details and safe entity references.",
      "Correct the cause and retry where supported.",
      "Use queue health for pending execution and return to logs for the final result."
    ],
    "fields": [
      "Queued or running: not completed success.",
      "Retry: can enqueue background work rather than finish immediately.",
      "Payloads: redacted diagnostics, never a reason to share credentials elsewhere."
    ],
    "tips": [
      "Do not duplicate retries when the task is already queued."
    ],
    "examples": [
      "A log shows failure, reference and timing; multiple stages do not necessarily mean duplicate sales."
    ],
    "troubleshooting": [
      "Retry is unfinished: inspect the current job and queue health before starting another attempt."
    ]
  },
  {
    "id": "queue-health",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Integration queue health and interrupted runs",
    "paths": [
      "/admin/integrations/queue-health"
    ],
    "paragraphs": [
      "Monitor pending and failed work, task age and execution evidence. This screen does not start the server worker."
    ],
    "steps": [
      "Inspect queue driver, counts, oldest age and worker-state hints.",
      "Open execution details for progress, heartbeat and safe errors.",
      "After correcting a supported failure, retry only if no task is already queued.",
      "Record an interruption only after confirming execution stopped and reading the confirmation.",
      "Copy the displayed worker command for server administration when needed; run it on the server or through Supervisor."
    ],
    "fields": [
      "Count scope: queue counts cover the current client stores; displayed sync logs cover the selected store.",
      "Idle: an empty queue alone does not prove a worker is running or stopped.",
      "Record interruption: marks the log failed with audit evidence; it neither kills a process nor retries automatically."
    ],
    "tips": [
      "Slow execution alone is not proof of interruption. Historical errors never recorded cannot be reconstructed here."
    ],
    "examples": [
      "Queue totals can cover the client’s stores while the displayed sync log remains store-scoped."
    ],
    "troubleshooting": [
      "Stale without activity: inspect worker and logs; marking interrupted does not start a worker."
    ]
  },
  {
    "id": "send-message",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Send customer messages or offers",
    "paths": [
      "/admin/notifications/send"
    ],
    "paragraphs": [
      "Send real messages to selected customers through ready channels, with customer/store placeholders and preview."
    ],
    "steps": [
      "Write subject and body using {{customer_name}} and {{store_name}} when needed.",
      "Choose ready channels; configure notification channels first if none are ready.",
      "Search with at least two characters and select customers, or use the eligible all-active option.",
      "Review preview and recipient count, send and read queued/skipped results.",
      "Open delivery records to track individual outcomes."
    ],
    "fields": [
      "All customers: active customers with an order or cart here under the screen rules, capped at 300.",
      "Preview: sample placeholder rendering, not delivery.",
      "Queued: delivery attempts accepted, not confirmed receipt."
    ],
    "tips": [
      "Review audience and content carefully. Viewing this screen does not necessarily grant execution permission."
    ],
    "examples": [
      "Start with an approved test recipient, preview name and store substitutions and review delivery before a group send."
    ],
    "troubleshooting": [
      "Queued but not received: inspect Deliveries, channel, worker and failure or skip reason."
    ]
  },
  {
    "id": "notification-templates",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Notification templates and placeholders",
    "paths": [
      "/admin/notifications/templates",
      "/admin/notifications/templates/new",
      "/admin/notifications/templates/create",
      "/admin/notifications/templates/:id/edit"
    ],
    "paragraphs": [
      "Templates define event/channel/language messages. Saving one does not itself send a notification."
    ],
    "steps": [
      "Filter event, channel or language and find existing templates.",
      "Choose event, channel and language and enter subject, body and status.",
      "Use supported placeholders such as {{order_number}} or {{customer_name}} and inspect the preview.",
      "Save and review the list, or read confirmation before deleting."
    ],
    "fields": [
      "Event: the trigger requesting a message.",
      "Channel and language: identify the required message version.",
      "Placeholders: missing data can render empty, so check the surrounding wording."
    ],
    "tips": [
      "A template also requires an enabled delivery channel, provider and relevant event configuration."
    ],
    "examples": [
      "One event can have Arabic and English content and channel-specific wording."
    ],
    "troubleshooting": [
      "Editing a template did not send anything: saving does not trigger an event; check event activation, channel and deliveries."
    ]
  },
  {
    "id": "notification-deliveries",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Notification deliveries and attempts",
    "paths": [
      "/admin/notifications/deliveries"
    ],
    "paragraphs": [
      "Track event, channel, recipient, state and attempt count to distinguish queued work from successful or failed delivery."
    ],
    "steps": [
      "Search recipient or event and apply available channel and status filters.",
      "Inspect available failure information and correct recipient or channel setup when necessary.",
      "Retry eligible records and monitor the outcome before trying again."
    ],
    "fields": [
      "Attempts: recorded processing attempts.",
      "Status: the recorded delivery stage, not proof that a customer read the message."
    ],
    "tips": [
      "Provider acceptance does not equal reading. Interpret outcomes according to the channel."
    ],
    "examples": [
      "Queued then Sent differs from Failed or Skipped; inspect the reason before retry."
    ],
    "troubleshooting": [
      "Invoice preparation failed: inspect the recorded reason, order data, recipient and channel."
    ]
  },
  {
    "id": "audit",
    "group": "operations",
    "group_title": "Integrations and notifications",
    "title": "Audit log and change attribution",
    "paths": [
      "/admin/system/audit-logs",
      "/admin/system/audit-logs/:id"
    ],
    "paragraphs": [
      "Review recorded administrative changes, actors, actions, times and affected records."
    ],
    "steps": [
      "Search and filter using the available actor, action, entity and date controls.",
      "Open a record and inspect its change summary and before/after data where recorded.",
      "Use references and timestamps when investigating changes, then correct data through its original screen."
    ],
    "fields": [
      "Actor: the recorded user or process.",
      "Entity: the affected record.",
      "Data: available audit evidence rather than provider secrets or passwords."
    ],
    "tips": [
      "Viewing an audit record does not undo it. Audit access requires its own permission."
    ],
    "examples": [
      "Inspect actor and edit time for an unexpected product price and compare the external update log."
    ],
    "troubleshooting": [
      "Expected event missing: check store, period, filters and operation type; the log only shows recorded activity."
    ]
  },
  {
    "id": "settings",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "General settings and out-of-stock visibility",
    "paths": [
      "/admin/settings/general"
    ],
    "paragraphs": [
      "Configure site name, tagline, support contacts and out-of-stock presentation. Navigate settings using the main sidebar."
    ],
    "steps": [
      "Check the active store and edit site name, tagline, support email and phone.",
      "Choose whether out-of-stock products remain visible.",
      "Save and wait for success, or discard to restore loaded values.",
      "Review the storefront consuming the setting."
    ],
    "fields": [
      "Out-of-stock visibility: off hides unavailable products; on keeps them visible without allowing purchase.",
      "False and zero: valid values rather than empty input.",
      "Unsaved changes: the save bar indicates differences from stored values."
    ],
    "tips": [
      "Some settings explicitly warn that storefront enforcement may still be pending; read those hints."
    ],
    "examples": [
      "Show out-of-stock products allows visibility without making unavailable items purchasable."
    ],
    "troubleshooting": [
      "A setting did not persist: inspect unsaved-change controls and save feedback, then reopen."
    ]
  },
  {
    "id": "store-profile",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Store profile, branding and logo",
    "paths": [
      "/admin/settings/store"
    ],
    "paragraphs": [
      "Manage translated store names, country code, timezone and visible branding, with default language and currency information."
    ],
    "steps": [
      "Edit translated names, country code and correct timezone, then save.",
      "Upload a logo or choose it from the library and inspect the preview and result.",
      "Use the available branding editor for the site icon and inspect the storefront.",
      "Change defaults through the dedicated language and currency screens."
    ],
    "fields": [
      "Timezone: affects store reporting day boundaries.",
      "Logo: JPEG, PNG, WebP or GIF, up to 2 MB under the upload hint.",
      "Code: the displayed store identifier, separate from translated names."
    ],
    "tips": [
      "Domain routing belongs to platform store administration, not the store profile form."
    ],
    "examples": [
      "A saved store logo appears in supported places such as order documents and invoices."
    ],
    "troubleshooting": [
      "Missing logo: inspect upload, size and format, save and check the intended output."
    ]
  },
  {
    "id": "languages",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Store languages and default language",
    "paths": [
      "/admin/settings/languages"
    ],
    "paragraphs": [
      "Attach an existing language or define one, then configure names, direction and availability."
    ],
    "steps": [
      "Add a language and choose an existing reference or a new definition.",
      "Complete code, translated names, native name and direction, then save.",
      "Set the default through its row action and enable or disable other languages.",
      "Review translated products and pages before offering a newly enabled language."
    ],
    "fields": [
      "Code: language identifier such as ar or en.",
      "Direction: right-to-left or left-to-right.",
      "Default: the store main language; choose a replacement before disabling it."
    ],
    "tips": [
      "Changing the default does not translate products or rewrite historical content."
    ],
    "examples": [
      "Changing the default store language does not translate product content automatically."
    ],
    "troubleshooting": [
      "Default language deactivation rejected: choose an appropriate replacement first."
    ]
  },
  {
    "id": "currencies",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Store currencies and exchange rates",
    "paths": [
      "/admin/settings/currencies"
    ],
    "paragraphs": [
      "Manage enabled/default currencies and store-specific names, symbols, display precision and exchange rates."
    ],
    "steps": [
      "Add a currency by linking an existing one or creating a definition.",
      "Enter code, names, symbol, display decimals and store base exchange rate.",
      "Set an optional custom rate to override the base rate in this store, then save.",
      "Choose the default and inspect the effective rate and gateway compatibility."
    ],
    "fields": [
      "Exchange rate: currency units per one US dollar, not the inverse.",
      "Custom rate: overrides the store base rate only here.",
      "Default: cannot be disabled before selecting a replacement."
    ],
    "tips": [
      "Changing the default does not recalculate historical orders. Keep report currencies separate."
    ],
    "examples": [
      "If a currency is 50 units per dollar, enter 50 rather than 0.020 under that field’s direction."
    ],
    "troubleshooting": [
      "Unexpected conversion: inspect global and store-specific exchange rates, default currency and display precision."
    ]
  },
  {
    "id": "checkout-settings",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Checkout, tax and invoice identity",
    "paths": [
      "/admin/settings/checkout"
    ],
    "paragraphs": [
      "Configure login requirements, tax calculation and legal seller details used for tax invoices."
    ],
    "steps": [
      "Choose whether checkout requires sign-in or allows guests.",
      "Set tax enabled, percentage, inclusive pricing and tax on shipping.",
      "Enter legal name, tax and commercial registration, address and invoice prefix as needed.",
      "Set product images in PDFs, save and test a new cart calculation."
    ],
    "fields": [
      "Inclusive: 115.000 including 15 percent tax gives 100.000 net plus 15.000 tax.",
      "Exclusive: 100.000 plus 15 percent tax gives 115.000 total.",
      "Login required: controls checkout rather than guest cart creation alone."
    ],
    "tips": [
      "Tax changes affect new carts and orders, not automatic recalculation of existing orders.",
      "Review product tax classes for specific treatment or rates."
    ],
    "examples": [
      "A 115.000 tax-inclusive amount at 15% has base 100.000 and tax 15.000; exclusive mode is different."
    ],
    "troubleshooting": [
      "Old invoice unchanged: values were saved at order or issue time; current settings do not rewrite them."
    ]
  },
  {
    "id": "auth-settings",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Customer sign-in and OTP verification",
    "paths": [
      "/admin/settings/auth"
    ],
    "paragraphs": [
      "Configure password, OTP or combined sign-in and verification channels, expiry and rate limits."
    ],
    "steps": [
      "Choose OTP-only, password-or-OTP or password mode.",
      "Set allowed, primary and fallback channels and inspect email/WhatsApp readiness.",
      "Set code length, validity, resend delay, attempt limit and sending-window limits.",
      "Choose automatic registration or existing-account requirements, save and test a ready channel."
    ],
    "fields": [
      "OTP-only: disables password login in storefront capabilities.",
      "Expiry and cooldown: measured in seconds as labeled.",
      "Fallback: an allowed configured alternative, not a substitute for provider readiness."
    ],
    "tips": [
      "Configure and enable the WhatsApp/email provider in notification channels first.",
      "Test before making a channel the only sign-in method, and keep customer codes private."
    ],
    "examples": [
      "An OTP channel must be both allowed and ready before relying on it as the main login method."
    ],
    "troubleshooting": [
      "OTP missing: check channel, provider, recipient and resend delay instead of rapid repeated requests."
    ]
  },
  {
    "id": "notification-settings",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Notification channels, providers and events",
    "paths": [
      "/admin/settings/notifications",
      "/admin/settings/notifications/:channel"
    ],
    "paragraphs": [
      "Configure actual email, WhatsApp, SMS and other supported sending channels, including provider credentials and events."
    ],
    "steps": [
      "Open a channel and choose a provider you have configured externally.",
      "Complete its displayed connection, sender, identifier and secret fields and save.",
      "Enable the channel and select permitted notification events.",
      "Check readiness, send an intentional test to a test recipient and inspect delivery records."
    ],
    "fields": [
      "Provider: supported options such as SMTP, Postmark or Mailgun and available WhatsApp/SMS providers.",
      "Saved secret: preserved by blank inputs where indicated; original values stay hidden.",
      "Events: system messages permitted through the channel.",
      "Invoice email BCC recipients are saved per store in email settings; review them when support or accounting recipients change."
    ],
    "tips": [
      "Activation without valid provider details is not readiness. Test a small delivery before a large audience.",
      "Public contact links are separate from notification delivery channels.",
      "Wajeez WhatsApp needs its correct connection settings. OTP wording can rotate automatically without changing the code or expiry; this is separate from an order-event template."
    ],
    "examples": [
      "Invoice BCC copies differ from visible customer recipient addresses."
    ],
    "troubleshooting": [
      "Enabled but not ready: complete required provider fields and secrets, save and inspect readiness."
    ]
  },
  {
    "id": "mobile-app",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Mobile-app versions and update message",
    "paths": [
      "/admin/settings/mobile-app"
    ],
    "paragraphs": [
      "These settings are client-wide and apply to all its stores, rather than only the selected store."
    ],
    "steps": [
      "Check the client code and scope notice.",
      "For Android or iOS, set update enforcement, latest version such as 1.2.0 and HTTPS store URL.",
      "Enter Arabic and English update messages, save and wait for confirmation.",
      "Test older and equal/newer app versions in the supporting application."
    ],
    "fields": [
      "Latest version: the version used for comparison.",
      "Enabled: older versions require updating; equal or newer versions do not.",
      "Update URL: the platform download destination."
    ],
    "tips": [
      "Switching stores within the same client does not create separate settings. Verify both platform URLs."
    ],
    "examples": [
      "App settings apply across the client’s stores; review Android and iOS fields separately."
    ],
    "troubleshooting": [
      "Update notice absent: check activation, installed-versus-configured version and the correct download link."
    ]
  },
  {
    "id": "tax-classes",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Tax classes and product assignment",
    "paths": [
      "/admin/settings/tax-classes",
      "/admin/settings/tax-classes/new",
      "/admin/settings/tax-classes/:id/edit"
    ],
    "paragraphs": [
      "Define tax treatment or rates and assign them to products, with one active default class per store."
    ],
    "steps": [
      "Review existing classes and enter translated names, code and description.",
      "Choose treatment, rate and status and mark the intended store default.",
      "Save and optionally assign the class in product relationships.",
      "Test a new cart and inspect its tax calculation."
    ],
    "fields": [
      "Rate: percentage interpreted according to treatment.",
      "Default: fallback when a product has no specific class under system precedence.",
      "Product class: optional; calculation falls back to default class, then general tax settings."
    ],
    "tips": [
      "Changing a rate does not correct an old invoice automatically; existing orders retain financial snapshots."
    ],
    "examples": [
      "Review a product’s specific tax class before changing the store-wide default."
    ],
    "troubleshooting": [
      "Unexpected tax: inspect product class, default class and inclusive or exclusive configuration."
    ]
  },
  {
    "id": "gateways",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Payment gateways, credentials and callback URLs",
    "paths": [
      "/admin/settings/payment-gateways",
      "/admin/settings/payment-gateways/:id"
    ],
    "paragraphs": [
      "Configure available methods such as COD, bank transfer, wallet, MyFatoorah, Paymob, Tap, Tabby, Hesabe, KPay and Deema."
    ],
    "steps": [
      "Open a gateway and inspect enabled state, test/stub mode, currencies and readiness fields.",
      "Enter the merchant details shown by its form; blank secret inputs preserve values where indicated. Save.",
      "Copy the exact return and webhook URLs into the provider dashboard; they contain client and store context.",
      "Run an approved test and inspect payment and webhook records before enabling a ready live configuration."
    ],
    "fields": [
      "Stub mode: does not make a real charge; distinct from an actual provider sandbox when supported.",
      "Ready: requires valid mandatory details and compatible configuration, not only an enabled toggle.",
      "Return and webhook: separate functions; provider evidence confirms payment."
    ],
    "tips": [
      "Deema supports KWD; inspect gateway currency and country restrictions.",
      "Authorization is not final capture where the gateway requires capture."
    ],
    "examples": [
      "Enable a method after readiness for the intended currency and fulfillment, then verify an approved test payment."
    ],
    "troubleshooting": [
      "Gateway absent: check activation, readiness, currency, shipping method and checkout requirements."
    ]
  },
  {
    "id": "gateway-fields",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Provider-specific fields and capture confirmation",
    "paths": [],
    "paragraphs": [
      "Each gateway needs different merchant details. Use the gateway form and approved credentials without putting secrets in notes or support messages."
    ],
    "steps": [
      "For Tap, check the secret key; for Tabby, secret key, merchant code and webhook secret.",
      "For Hesabe, check merchant code, access code, secret and IV key.",
      "For KPay, check tranportal ID, password, 16-character resource key, displayed response URL and KWD currency code 414 where required.",
      "For Deema, check API key, webhook secret, environment and compatible currency.",
      "Complete the required fields of other provider forms and inspect readiness before enabling."
    ],
    "fields": [
      "Tap: final collection uses confirmed CAPTURED status.",
      "Tabby: collection follows the supported capture flow.",
      "Hesabe and KPay: response integrity and amount are checked.",
      "Deema: captured or fully_captured represents collection, not authorized alone.",
      "Tabby signature: webhook secret uses X-Tabby-Signature under provider configuration.",
      "Deema signature: the default header is x-deema-signature; inspect the configured gateway value."
    ],
    "tips": [
      "Do not mix credentials between providers. Hidden values do not mean saving failed."
    ],
    "examples": [
      "Authorized is not Captured for providers that separate authorization and collection."
    ],
    "troubleshooting": [
      "Payment response rejected: inspect currency, amount, reference, signature verification and provider logs."
    ]
  },
  {
    "id": "tracking",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Tracking providers, pixels and events",
    "paths": [
      "/admin/settings/tracking",
      "/admin/settings/tracking/:id"
    ],
    "paragraphs": [
      "Configure marketing/analytics identifiers and events while keeping credentials separate from public settings."
    ],
    "steps": [
      "Open a provider and inspect state, readiness and missing required fields.",
      "Enter public IDs in configuration and secrets only in credentials.",
      "Choose events and order, save and enable when ready.",
      "Read the disable confirmation; scripts and events stop while saved configuration remains."
    ],
    "fields": [
      "Ready: required fields pass panel checks.",
      "Events: sent where supported by the storefront and enabled provider.",
      "Clear all secrets: explicitly removes credentials, unlike leaving secret fields blank."
    ],
    "tips": [
      "Activation does not prove every event reached the provider; verify using provider tools without exposing keys."
    ],
    "examples": [
      "A public tracking ID differs from a credential; use each provider field as labeled."
    ],
    "troubleshooting": [
      "Missing events: inspect storefront support, provider and event activation and required fields."
    ]
  },
  {
    "id": "staff",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Staff, store assignment and roles",
    "paths": [
      "/admin/access/staff",
      "/admin/access/staff/create",
      "/admin/access/staff/:id/edit"
    ],
    "paragraphs": [
      "Manage staff access to stores and roles. The form previews screens available to the selected role."
    ],
    "steps": [
      "Search by name or email, then choose a new account or invite an existing account as supported by the form.",
      "For a new account enter name, email, password and confirmation. Inviting an existing account grants store assignment without changing its identity or password.",
      "Choose permitted stores, role and assignment status, review the screen preview, save and verify success.",
      "When editing, review role, stores and editable account fields. Leave password blank to keep it unchanged.",
      "Use the row action to log out all devices, verify the named account and confirm. Applying it to yourself also ends your session.",
      "Removing a store assignment differs from account deactivation or session revocation. Review the effect before confirmation."
    ],
    "fields": [
      "Password: at least eight characters under the form rules.",
      "Stores: only assigned stores are available to the employee.",
      "Role: applies in assigned stores and determines available screens.",
      "Log out all devices revokes the targeted account’s sessions with staff-management permission; it does not remove historical orders or change the role."
    ],
    "tips": [
      "Safeguards protect the last store manager and restricted self-demotion or deactivation.",
      "Super Admin is protected and cannot be assigned as a store-staff role.",
      "Account and store operations are limited by the acting user’s authority. The last store manager, staff-management access and Super Admin have special protections."
    ],
    "examples": [
      "Inviting existing staff to a store is not a way to reset their email or password."
    ],
    "troubleshooting": [
      "Manager removal rejected: inspect last-manager protections and the actor’s authority before changing access."
    ]
  },
  {
    "id": "roles",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Roles and permissions",
    "paths": [
      "/admin/access/roles",
      "/admin/access/roles/new",
      "/admin/access/roles/:roleId"
    ],
    "paragraphs": [
      "A role groups permissions for multiple staff accounts. Saving changes affects staff using that role within assigned stores."
    ],
    "steps": [
      "Inspect whether a role is system, custom and assignable.",
      "Create a custom role or open an editable role and complete allowed name/description fields.",
      "Select required screen and action permissions, save and review employee access.",
      "Reassign linked staff before deleting a role when required."
    ],
    "fields": [
      "System role: fixed name with editable description and permissions where allowed.",
      "Super Admin: locked and not edited here.",
      "Screen permission: controls visibility and route access; a general module permission alone is insufficient.",
      "An empty saved permission set grants no permissions; it does not automatically restore a system catalog."
    ],
    "tips": [
      "Customized roles follow saved permissions; inspect viewing and editing separately.",
      "Grant sensitive actions only when needed, rather than to enable list viewing.",
      "Customized roles use their saved choices. Check screen access separately from action permissions and verify an allowed and a denied path."
    ],
    "examples": [
      "Grant payment viewing separately from refund authority; inspect financial actions independently."
    ],
    "troubleshooting": [
      "Saved role but missing screen: inspect its specific permission, store and session; module permission alone is insufficient."
    ]
  },
  {
    "id": "permissions",
    "group": "settings",
    "group_title": "Settings and access",
    "title": "Permissions catalog",
    "paths": [
      "/admin/access/permissions"
    ],
    "paragraphs": [
      "Read permission keys, descriptions, groups and sensitivity markers. This screen does not directly change employee access."
    ],
    "steps": [
      "Search the permission key or available description.",
      "Review its group and sensitive marker.",
      "Assign it through a role, then assign that role to the staff member."
    ],
    "fields": [
      "Permission key: the catalog technical identifier for review.",
      "Sensitive: identifies an action requiring care, rather than blocking an authorized user."
    ],
    "tips": [
      "The catalog is read-only; permission definitions cannot be edited here."
    ],
    "examples": [
      "orders.create allows order creation; reports.staff_sales.view controls the order-entry report."
    ],
    "troubleshooting": [
      "A listed catalog key is not automatically granted; assign it through an authorized role change."
    ]
  },
  {
    "id": "platform-stores",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Platform stores and store details",
    "paths": [
      "/platform/stores",
      "/platform/stores/:id"
    ],
    "paragraphs": [
      "Authorized platform administrators manage store identities, state, statistics and onboarding. This differs from operating one store."
    ],
    "steps": [
      "Search name, code or domain and apply status filters.",
      "Open a store to review identity, state, statistics and management actions.",
      "Enter the store to switch context and verify its name in the panel header.",
      "Read the scope and confirmation of edits or deactivation; review readiness before launch."
    ],
    "fields": [
      "State: store activity or readiness within platform rules.",
      "Statistics: summary indicators rather than complete operational reports.",
      "Enter store: switches context without copying its data."
    ],
    "tips": [
      "Platform permissions exceed ordinary store-staff access, so missing platform screens can be expected."
    ],
    "examples": [
      "Entering a store from Platform switches context; verify its name before editing."
    ],
    "troubleshooting": [
      "A store is not ready: inspect readiness blockers rather than changing unrelated settings."
    ]
  },
  {
    "id": "platform-create",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Create a store and review its preview",
    "paths": [
      "/platform/stores/create"
    ],
    "paragraphs": [
      "Create store identity and initial configuration, optionally from a safe template, with validation before execution."
    ],
    "steps": [
      "Complete identity, code, country, localization and the required wizard fields.",
      "Choose an available template or safe sections and configure access as requested.",
      "Preview and inspect blocking errors and warnings.",
      "Correct inputs, submit creation once, wait for completion and open onboarding."
    ],
    "fields": [
      "Code: unique validated store identifier.",
      "Template: selected initial configuration rather than customer data from another store.",
      "Preview: proposed creation details and warnings."
    ],
    "tips": [
      "Creation is not immediate public launch. Complete readiness, integration and domain setup first."
    ],
    "examples": [
      "Preview a new store with its own identity and review readiness before launch."
    ],
    "troubleshooting": [
      "Creation rejected: correct identity, uniqueness and displayed blockers and preview again."
    ]
  },
  {
    "id": "platform-edit",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Edit a store from platform administration",
    "paths": [
      "/platform/stores/:id/edit"
    ],
    "paragraphs": [
      "Authorized administrators edit the store identity, localization and legal fields exposed by the form."
    ],
    "steps": [
      "Open the correct store and verify name and code.",
      "Edit permitted identity, country, language, currency, timezone and legal details.",
      "Save, inspect confirmation and review readiness if relevant inputs changed."
    ],
    "fields": [
      "Identity: store identification and presentation.",
      "Localization: available language, currency and time fields."
    ],
    "tips": [
      "Identity changes do not recalculate old orders. Domain management has its own checks."
    ],
    "examples": [
      "Renaming a store is different from choosing its primary domain or copying another store."
    ],
    "troubleshooting": [
      "A field is not editable: use supported fields and the account’s platform authority."
    ]
  },
  {
    "id": "platform-readiness",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Store onboarding and launch readiness",
    "paths": [
      "/platform/stores/:id/onboarding",
      "/platform/stores/:id/readiness"
    ],
    "paragraphs": [
      "Checks identify launch blockers and follow-up warnings, with repair links where permission permits."
    ],
    "steps": [
      "Open onboarding and refresh checks.",
      "Address blockers through their repair screens and save corrections.",
      "Refresh readiness; warnings differ from mandatory blockers.",
      "After all blockers pass, review final setup and launch only when intended and authorized."
    ],
    "fields": [
      "Blockers: mandatory requirements before launch.",
      "Warnings: follow-up items distinct from launch prevention.",
      "Degraded: an active store no longer meeting some readiness requirements."
    ],
    "tips": [
      "Deactivation retains data but removes availability. It is not a way to refresh checks."
    ],
    "examples": [
      "After fixing a gateway, refresh readiness checks to see the updated result."
    ],
    "troubleshooting": [
      "A blocker remains: inspect that check and refresh after saving the fix; warnings differ from blockers."
    ]
  },
  {
    "id": "platform-domains",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Store domains, verification and SSL",
    "paths": [
      "/platform/stores/:id/domains"
    ],
    "paragraphs": [
      "Link domains or subdomains and inspect ownership, routing and certificate checks before relying on them."
    ],
    "steps": [
      "Add type, host or subdomain, status and optional primary redirect.",
      "Save and follow the exact verification DNS instructions with the domain administrator.",
      "After DNS propagation, check ownership, routing and SSL separately.",
      "Make the domain primary only when ready and test its redirects.",
      "Read the impact before rotating verification tokens or deleting a domain."
    ],
    "fields": [
      "Ownership: control of the domain, separate from correct routing.",
      "Routing: whether traffic reaches the intended service.",
      "SSL: secure certificate validity.",
      "Primary: the canonical domain used by supported redirects."
    ],
    "tips": [
      "Saving here does not automatically update external DNS, and checks can wait for propagation."
    ],
    "examples": [
      "A verified domain can still have incorrect routing or SSL; review all three checks."
    ],
    "troubleshooting": [
      "Domain fails: review DNS instructions, routing, certificate and propagation with its administrator."
    ]
  },
  {
    "id": "store-templates",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Store templates and template creation",
    "paths": [
      "/platform/store-templates",
      "/platform/store-templates/:id",
      "/platform/store-templates/create"
    ],
    "paragraphs": [
      "A template reuses selected safe configuration for new stores without operational data or secrets."
    ],
    "steps": [
      "Inspect existing template details, country, type and included sections.",
      "Create a template with name, description, source store and selected safe sections.",
      "Save and review it, then use create store when needed.",
      "Read confirmation before deleting a custom template; existing stores remain unchanged."
    ],
    "fields": [
      "System or custom: template origin and available management actions.",
      "Sections: only the safe configuration included.",
      "Source: the configuration donor, not a copy of all operational content."
    ],
    "tips": [
      "This flow excludes customers, orders, payments, wallets, staff, domains and secrets."
    ],
    "examples": [
      "A shipping/localization template does not carry source orders, balances or credentials."
    ],
    "troubleshooting": [
      "Expected section missing: inspect supported safe sections and the template selection."
    ]
  },
  {
    "id": "store-clone",
    "group": "platform",
    "group_title": "Platform administration",
    "title": "Clone store configuration with preview",
    "paths": [
      "/platform/stores/:id/clone"
    ],
    "paragraphs": [
      "Create a new inactive store from safe source configuration without copying customer or sales activity."
    ],
    "steps": [
      "Open clone from the intended source and inspect its scope.",
      "Enter target identity, access and available sections.",
      "Preview record counts, blocking errors and warnings.",
      "Correct inputs, create the clone once and complete onboarding before launch."
    ],
    "fields": [
      "Source and target: separate stores; the target starts inactive.",
      "Preview: validates the proposed copy before creation.",
      "Exclusions: customers, orders, payments, wallets, staff, domains, secrets and operational data."
    ],
    "tips": [
      "Cloning is not a sales transfer and does not automatically enable live gateways."
    ],
    "examples": [
      "A cloned configuration starts inactive and needs review; it does not transfer source customers or sales."
    ],
    "troubleshooting": [
      "Clone not launched: finish its own readiness and connection checks before use."
    ]
  },
  {
    "id": "troubleshooting",
    "group": "start",
    "group_title": "Getting started",
    "title": "Troubleshooting and outcome checks",
    "paths": [],
    "paragraphs": [
      "Start with store context, filters, permissions and the actual error, then inspect the original record or follow-up screen."
    ],
    "steps": [
      "Missing screen: review store assignment and its specific screen permission, then refresh the session if needed.",
      "Missing record: clear filters and search, inspect pagination and any deleted-record filter.",
      "Missing discount: inspect dates, activation, product selection and offer type; cart coupons differ from product price campaigns.",
      "Wrong shipping price: inspect method, location IDs, conditions, free shipping and area/city/country priority.",
      "Dashboard mismatch: align dates, timezone, currency and metric definition, then inspect financial overview and transactions.",
      "Undelivered message: inspect channel readiness and delivery logs rather than template-save success alone.",
      "Delayed sync: review queue health, heartbeat and logs before retrying or recording interruption."
    ],
    "fields": [
      "Rejected save: inspect field errors for invalid dates, duplicates, relationships or missing permissions.",
      "Empty list: can be a filter result rather than deletion.",
      "Success: confirmation plus a visible updated result, not a click alone."
    ],
    "tips": [
      "For support, provide screen, store, reference, steps and error message without passwords, keys or verification codes."
    ],
    "examples": [
      "A half-hour-old cart is hidden by the one-day inactivity filter; choose Any activity in the correct store."
    ],
    "troubleshooting": [
      "If it persists, provide store, screen, record reference, time, error and attempted steps without credentials."
    ]
  }
]
