How NOTIWOO works

The app coordinates orders and operations; WordPress and WooCommerce hold the catalog and plugin storefront features. Supabase manages authentication, permissions, operational data and real-time events.

Components and connections

The app uses React, Zustand and ES/EN translations. Adapters separate the interface from Supabase and the woo-api function. That function communicates with WooCommerce and the plugin API without exposing store credentials in the browser.

Orders and sales

Webhooks feed order events and Realtime updates the app. A fallback query helps recover changes missed by the live channel. Table and Kanban consume the same collection.

The new workflow distinguishes preparation, delivery and sale closure. It records synchronization and conflicts with external changes. Delivery maintains related assignments and collections; closure should not be inferred from Completed alone.

Role access

The session is checked before opening a protected route. Roles and permissions determine menus, actions and landing sections. Couriers use a dedicated interface. NotiChat adds station-level enablement and excludes couriers.

Tracking, notifications and AI

GPS requires consent and limited sessions. Public links show statuses and approximate location during delivery. WhatsApp depends on consent, templates and quota.

NotiChat queries data through tools and presents proposals before executing changes. Permissions follow the user. Conversations, memories and results need the same care as other business data.

Printing and limits

The local service prints according to language, currency, copies and configured fields; receipts may include table and service mode.

The operational view loads the 200 most recent order events. Real-time availability depends on connectivity, webhooks and Supabase. Documentation screenshots use simulated responses and a local shop without accessing real accounts.