Sekani Empire Online Ordering

Custom WordPress/WooCommerce plugin for remote pickup and delivery orders, a menu/cart interface, staff notifications and optional Google Sheets tracking.

Local source version: 1.11.0. Publication copy: internal notification addresses removed and the spreadsheet ID replaced with a placeholder. Original local files and the live site are unchanged.

Requirements and installation

• WordPress 6.0+, PHP 7.4+ (original declared minimums), and WooCommerce.
• Use supported runtime versions; full version compatibility has not been certified by this repository preparation.
• Paystack/Flutterwave payments require separately installed gateway plugins and privately configured accounts/keys. These plugins and keys are not bundled.
• Install on a separate WordPress site from the three in-house venue plugins.

1. Install and activate WooCommerce on an isolated staging site first.
2. Put the repository's plugin files and assets/ into a folder named sekani-empire-ordering; ZIP that folder.
3. Upload via Plugins > Add New Plugin > Upload Plugin and activate.
4. Create a Menu page using [sekani_empire_menu] and an About Us page using [sekani_empire_about].
5. Set Menu as the static homepage. Confirm WooCommerce's Cart and Checkout pages exist.
6. The plugin creates a protected frontend dashboard at /admin/; an existing page at that slug must contain [sekani_empire_admin].
7. Configure business details, real menu items/images, delivery regions/fees, notification recipients and optional Sheets tracking in the dashboard.
8. Configure payment gateways privately, test checkout in test mode, and validate live account activation separately before taking real payments.

Activation side effects: the code turns off WooCommerce Coming Soon mode, synchronizes the sample/saved menu into hidden-catalog WooCommerce products, may download referenced product images, and can replace a block checkout with [woocommerce_checkout]. Do not activate on a live store without reviewing these effects.

Ordering and staff workflow

• WooCommerce-backed cart and checkout, with pickup or delivery.
• Delivery requires a selected region and street address. Town/city, state, postcode, country and apartment inputs are removed from the visible delivery form.
• Alternatively, Order via WhatsApp pre-fills a summary for the customer to review and send. Opening WhatsApp does not itself complete an online payment.
• Out-of-stock items are faded and blocked from adding to the cart, including server-side stock checks.
• Staff can mark orders ready for pickup, dispatched or completed and trigger branded customer emails.
• New-order alerts use the configured recipient list. The publication copy defaults to no recipients. Set and test recipients before launch; the plugin disables WooCommerce's standard new-order email.
• CSV menu import is not included in this ordering release.

Optional Google Sheets integration

google-sheets-app-script.txt is a source template, not an exported spreadsheet.

1. Create a private spreadsheet and replace PASTE_YOUR_SPREADSHEET_ID_HERE in a private Apps Script copy.
2. Copy the dashboard's connection secret into that private script's connection-secret placeholder.
3. Deploy the script as a Web App with permissions suitable for the server webhook.
4. Save the deployed URL in the WordPress dashboard and test using synthetic orders.
5. Keep the customized script, URL and connection secret out of Git.

The script creates/updates a Transactions tab. At runtime it receives customer names, email/phone, street address, items, amounts and order status. Restrict spreadsheet/script access and handle retention appropriately. No actual customer rows are included here. The supplied example must not be deployed with its placeholder secret.

Repository contents and privacy

• sekani-empire-ordering.php: menu rendering, defaults, shortcodes, dashboard and staff management.
• woocommerce-integration.php: cart, checkout, product sync, status/email and Sheets integrations.
• assets/: CSS and JavaScript.
• google-sheets-app-script.txt: sanitized Apps Script template.
• readme.txt: original plugin metadata/release history, with recipient setup corrected.

This is source code, not a full WordPress website backup. Saved menu settings, live products, customer orders, users and uploads reside separately in WordPress. No WordPress configuration/salts, credentials, gateway keys, database dumps, customer exports, operational email list, spreadsheet ID, screenshots or historical ZIPs are included.

The source retains Sekani branding, public-facing business contact defaults, example delivery fees, sample menu descriptions/prices and Unsplash image URLs. Replace defaults with approved production information. No original photographs or logo files are bundled.

Development and checks

There is no build step. Edit PHP and assets/ directly. Lint each PHP file with php -l FILE.php and JavaScript with node --check FILE.js when the runtimes are available.

Before deploying an update, test on a private staging site:

• Authorized versus unauthorized dashboard actions; save and reload.
• Menu/category changes and out-of-stock cart/checkout validation.
• Pickup versus delivery, region fee calculation and required street address.
• Gateway success, cancellation and failure using test mode.
• Notifications to configured test recipients, with no disclosure to other recipients.
• Ready/dispatched/completed customer emails and WhatsApp links.
• Sheets synchronization using synthetic customer data and a private test sheet.

Never use production customer data as fixtures. Back up production privately before deployment. The source-only Git allowlist requires explicit review for newly added paths.

Provenance and rights

Prepared on 20 September 2026 from local version 1.11.0, which matched the corresponding local release ZIP before the sanitization described above. The installed production version and current live settings have not been compared.

The original readme declares GPLv2 or later; this preparation preserves that declaration. Sekani trademarks, branding, business copy and third-party imagery are not automatically covered by the code license. Obtain the appropriate owner's approval before public publication.