Athenian Order Fulfillment Statuses for WooCommerce
Overview
Product overview
WooCommerce order statuses are useful for high-level transaction state, but they are usually too coarse for fulfillment operations. Teams often need to know whether an order has been routed to a vendor, accepted by a supplier, moved into production, partially shipped, blocked by an exception, or waiting on a customer response. When that information lives in notes, spreadsheets, or ad hoc vendor messages, fulfillment becomes harder to manage, harder to search, and harder to export for downstream operations.
AOFS solves that by introducing a configurable fulfillment-status system directly into WooCommerce admin. It lets merchants define their own operational statuses, apply one or more statuses to each order, browse orders by fulfillment criteria, and export filtered order sets as CSV for handoff, reporting, or vendor coordination.
Use cases
- Fulfillment operations
- Order lifecycle
- Warehouse handoffs
- Customer status visibility
Developer
Developer starting point
This baseline documents the reviewed order-status implementation. It does not claim that a live order transition, fulfillment event, customer notification, or downstream shipment effect has been exercised.
Ecosystem integration story
WooCommerce admin workflows
AOFS is built to extend WooCommerce admin rather than replace it. It attaches fulfillment metadata to orders, exposes that metadata in list tables, and makes it queryable through familiar admin filters and order-management screens.
HPOS compatibility
AOFS declares compatibility with WooCommerce High-Performance Order Storage and supports both legacy and HPOS order list experiences. That gives merchants a fulfillment workflow layer that remains aligned with modern WooCommerce order storage architecture.
Dropship and vendor-routed operations
AOFS is especially well suited to dropship-style operations because it includes seeded statuses such as Vendor Routed and Vendor Accepted and lets teams group and export those orders quickly. It gives operational teams a cleaner way to manage vendor-facing fulfillment stages without redefining customer-facing WooCommerce order states.
Broader Athenian operations
AOFS is not a shipping carrier plugin or warehouse management system. Its role is to make fulfillment state legible, manageable, and portable inside WooCommerce so downstream Athenian workflows can act on the right order cohorts at the right time.
Install
- Reviewed source folder: athenian-order-fulfillment-statuses
- Plugin version reviewed: 0.2.0
- Local source inventory: 8 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-order-fulfillment-statuses at main / e8d6c7c39708855c9b8fcde61bc774cede404352.
- WordPress and WooCommerce.
- Order transitions, fulfillment notifications, email delivery, vendor workflows, and downstream shipment effects require separate target verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem AOFS solves — see the linked technical reference excerpt.
- What AOFS does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 0
- Static action/filter hooks detected in local PHP source: 18
- REST route registrations detected in local PHP source: 0
Shortcodes
- No static add_shortcode registrations were detected by the baseline scanner.
REST Endpoints
- No register_rest_route calls were detected by the baseline scanner.
Hooks
- add_meta_boxes — includes/class-cofs-plugin.php
- admin_enqueue_scripts — includes/class-cofs-plugin.php
- admin_init — includes/class-cofs-plugin.php
- admin_menu — includes/class-cofs-plugin.php
- admin_notices — includes/class-cofs-plugin.php
- admin_post_ — includes/class-cofs-plugin.php
- before_woocommerce_init — custom-order-fulfillment-statuses.php
- manage_edit-shop_order_columns — includes/class-cofs-plugin.php
- manage_shop_order_posts_custom_column — includes/class-cofs-plugin.php
- manage_woocommerce_page_wc-orders_columns — includes/class-cofs-plugin.php
- manage_woocommerce_page_wc-orders_custom_column — includes/class-cofs-plugin.php
- plugins_loaded — custom-order-fulfillment-statuses.php
- plugin_action_links_ — includes/class-cofs-plugin.php
- pre_get_posts — includes/class-cofs-plugin.php
- restrict_manage_posts — includes/class-cofs-plugin.php
- woocommerce_order_list_table_prepare_items_query_args — includes/class-cofs-plugin.php
- woocommerce_order_list_table_restrict_manage_orders — includes/class-cofs-plugin.php
- woocommerce_process_shop_order_meta — includes/class-cofs-plugin.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 8a09a3b051e118604c04e6f49fa4d8ab501f0bae7e714130d1bc522a9bb72444
- Repository URL: https://github.com/Athenian-Brands/athenian-order-fulfillment-statuses
- Repository reference: main
- Repository commit: e8d6c7c39708855c9b8fcde61bc774cede404352
Source files include: assets/css/admin.css, assets/js/admin.js, athenian-order-fulfillment-status-icon.png, custom-order-fulfillment-statuses.php, docs/aofs-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, includes/class-cofs-plugin.php
Troubleshooting
This baseline documents the reviewed order-status implementation. It does not claim that a live order transition, fulfillment event, customer notification, or downstream shipment effect has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.