Athenian WooCommerce Dropship
Overview
Athenian WooCommerce Dropship
Athenian WooCommerce Dropship Developer Documentation
Overview
Athenian WooCommerce Dropship is a WooCommerce vendor-orchestration plug-in that adds vendor onboarding, vendor portals, competitive vendor offer handling, cart and Store API vendor selection, shipping package splitting, purchase-order generation, vendor email dispatch, shipment-label workflows, and payout-ready settlement snapshots.
In this repository snapshot, the plug-in acts as the supply-side execution layer of the broader Athenian Platform and is designed to work with:
- WooCommerce for cart, checkout, orders, shipping, and order-item storage
- Athenian Platform Core (required) for the canonical Vendor CPT and shared bridge patterns
- optional ACF field groups for vendor and PO data entry
- optional Athenian Print Forge and Product Add-ons order metadata for artwork, proofing, and production-file handoff
High-Level Architecture
The main bootstrap file is athenian-wc-dropship.php. It defines constants, registers the namespace autoloader, declares WooCommerce feature compatibility, checks for WooCommerce and Athenian Platform Core, and then defers all runtime bootstrapping to Athenian\WCDropship\Plugin.
At a high level, the plug-in is composed of seven layers:
- Bootstrap and compatibility declarations
- Vendor and storefront runtime wiring
- Cart and Store API vendor persistence
- Shipping package splitting and rate a
otation
- Purchase-order generation and vendor communications
- Shipment and payout workflows
- Admin, vendor onboarding, and portal surfaces
Bootstrap Sequence
Core constants and autoloading
The root plug-in file defines:
AB_WCDS_PATHAB_WCDS_URLAB_WCDS_VERSIONAB_WCDS_DEBUG
It also registers a PSR-4-ish autoloader for classes under Athenian\WCDropship\*, with a dashed-file fallback for class files such as class-vendor-portal-shortcode.php.
WooCommerce feature declarations
On before_woocommerce_init, the plug-in declares compatibility with:
custom_order_tablescart_checkout_blocksnew_product_editor
Activation and rewrite behavior
includes/Setup.php handles basic lifecycle work:
- activation sets
_ab_wcds_needs_flush=1 initloads the text domaininitflushes rewrites once after activation when needed
The main plug-in also registers the Woo My Account vendor endpoint during runtime.
Hard dependency on Athenian Platform Core
Plugin::__construct() exits early with an admin notice if APC_PATH is not defined. In practice, this plug-in expects Athenian Platform Core to provide the canonical Vendor CPT and shared platform wiring.
Primary boot path
Once WooCommerce is available, Plugin::instance() wires the major runtime modules:
- assets
- setup and admin classes
- vendor role and vendor-user linking helpers
- shortcodes and vendor profile routes
- APF vendor buybox integration
- PO subsystem
- shipping, email, PDF, and shipment label services
- REST controllers
Main Runtime Modules
1. Root orchestrator
The main runtime orchestrator lives in includes/Plugin.php.
Responsibilities:
- verifies Platform Core is present
- initializes feature modules
- exposes canonical meta keys such as
_apc_vendor_eligibleand_apc_vendor_offers - manages vendor role creation
- manages vendor post to user and user to vendor linking
- renders APF vendor buybox fallback HTML through the
ath/apc/vendor_buybox_htmlfilter
Important constants in this class include:
META_VENDOR_ELIGIBLE = _apc_vendor_eligibleMETA_VENDOR_OFFERS = _apc_vendor_offersMETA_VENDOR_USER_ID = _ab_vendor_user_idMETA_USER_VENDOR_ID = _ab_vendor_idROLE_VENDOR = vendor
2. Asset system
The front-end asset registry lives in includes/class-assets.php.
Responsibilities:
- registers cart, archive, vendor selector, buybox, profile, and APF bridge scripts
- registers vendor selector, buybox, and cart styles
- conditionally enqueues assets on product, cart, and archive-like views
- injects a shared
window.APC_CART_VENDOR_CFGpayload for front-end consumers
Notable registered handles include:
apc-cart-vendor-blocksapc-cart-vendor-singleapc-cart-vendor-archivesapc-vendor-selectorab-vendor-profileab-wcds-vendor-buyboxab-wcds-apf-vendor-bridge
3. Vendor resolution and offer storage
Vendor offer and resolution logic is split across:
includes/Vendors/VendorResolver.phpincludes/Vendors/VendorPricingOffers.php
VendorResolver handles fulfillment-oriented vendor eligibility and vendor selection rules.
Responsibilities:
- reads canonical fulfillment offers from
_apc_vendor_offers - falls back from variations to parent products
- supports legacy single-vendor meta synthesis
- treats unpi
ed cart items as Store by default
- resolves vendor origin data from vendor post meta
VendorPricingOffers handles pricing-offer persistence.
Responsibilities:
- stores vendor pricing offers in
_ab_vendor_pricing_offers - normalizes unit pricing, tiers, lead days, status, and source metadata
- supports per-vendor upserts for products and variations
- supports bulk upsert workflows for CSV/API ingestion
This separation is important:
_apc_vendor_offersis the canonical eligibility and storefront-offer surface_ab_vendor_pricing_offersis the vendor pricing-offer storage used by vendor ingestion/admin workflows
4. Cart and Store API vendor persistence
Cart vendor persistence is implemented across:
includes/Frontend/Cart/Cart_Vendor_Switcher.phpincludes/Frontend/Cart/Cart_Vendor_Store_Extension.phpincludes/Frontend/Cart/Cart_Vendor_REST.php
Cart_Vendor_Switcher handles classic cart UI.
Responsibilities:
- renders a vendor selector per cart line item
- writes selected vendor IDs to
apc_vendor_idcart item data - restores the value into the cart session on update
Cart_Vendor_Store_Extension handles the Store API and Blocks path.
Responsibilities:
- captures vendor IDs from Store API add-to-cart payloads
- persists vendor IDs under
apc_vendor_id - exposes vendor info under
extensions.apcin Store API item responses - hydrates offers from
_apc_vendor_offers - backstops cart responses when downstream extensions fail to inject data
Important namespace split:
- read namespace:
apc - write namespace:
ab-wcds-vendor
> Source excerpt shortened for the baseline web reference; the linked repository remains authoritative for the complete document.
Use cases
- Manual developer onboarding
- Admin and frontend workflow review
- Release and deployment reconciliation
Developer
Developer starting point
Use this baseline with the active plugin installation and linked repository. Confirm the deployed header version and dependency state before applying changes.
Athenian WooCommerce Dropship Developer Documentation
Overview
Athenian WooCommerce Dropship is a WooCommerce vendor-orchestration plug-in that adds vendor onboarding, vendor portals, competitive vendor offer handling, cart and Store API vendor selection, shipping package splitting, purchase-order generation, vendor email dispatch, shipment-label workflows, and payout-ready settlement snapshots.
In this repository snapshot, the plug-in acts as the supply-side execution layer of the broader Athenian Platform and is designed to work with:
- WooCommerce for cart, checkout, orders, shipping, and order-item storage
- Athenian Platform Core (required) for the canonical Vendor CPT and shared bridge patterns
- optional ACF field groups for vendor and PO data entry
- optional Athenian Print Forge and Product Add-ons order metadata for artwork, proofing, and production-file handoff
High-Level Architecture
The main bootstrap file is athenian-wc-dropship.php. It defines constants, registers the namespace autoloader, declares WooCommerce feature compatibility, checks for WooCommerce and Athenian Platform Core, and then defers all runtime bootstrapping to Athenian\WCDropship\Plugin.
At a high level, the plug-in is composed of seven layers:
- Bootstrap and compatibility declarations
- Vendor and storefront runtime wiring
- Cart and Store API vendor persistence
- Shipping package splitting and rate a
otation
- Purchase-order generation and vendor communications
- Shipment and payout workflows
- Admin, vendor onboarding, and portal surfaces
Bootstrap Sequence
Core constants and autoloading
The root plug-in file defines:
AB_WCDS_PATHAB_WCDS_URLAB_WCDS_VERSIONAB_WCDS_DEBUG
It also registers a PSR-4-ish autoloader for classes under Athenian\WCDropship\*, with a dashed-file fallback for class files such as class-vendor-portal-shortcode.php.
WooCommerce feature declarations
On before_woocommerce_init, the plug-in declares compatibility with:
custom_order_tablescart_checkout_blocksnew_product_editor
Activation and rewrite behavior
includes/Setup.php handles basic lifecycle work:
- activation sets
_ab_wcds_needs_flush=1 initloads the text domaininitflushes rewrites once after activation when needed
The main plug-in also registers the Woo My Account vendor endpoint during runtime.
Hard dependency on Athenian Platform Core
Plugin::__construct() exits early with an admin notice if APC_PATH is not defined. In practice, this plug-in expects Athenian Platform Core to provide the canonical Vendor CPT and shared platform wiring.
Primary boot path
Once WooCommerce is available, Plugin::instance() wires the major runtime modules:
- assets
- setup and admin classes
- vendor role and vendor-user linking helpers
- shortcodes and vendor profile routes
- APF vendor buybox integration
- PO subsystem
- shipping, email, PDF, and shipment label services
- REST controllers
Main Runtime Modules
1. Root orchestrator
The main runtime orchestrator lives in includes/Plugin.php.
Responsibilities:
- verifies Platform Core is present
- initializes feature modules
- exposes canonical meta keys such as
_apc_vendor_eligibleand_apc_vendor_offers - manages vendor role creation
- manages vendor post to user and user to vendor linking
- renders APF vendor buybox fallback HTML through the
ath/apc/vendor_buybox_htmlfilter
Important constants in this class include:
META_VENDOR_ELIGIBLE = _apc_vendor_eligibleMETA_VENDOR_OFFERS = _apc_vendor_offersMETA_VENDOR_USER_ID = _ab_vendor_user_idMETA_USER_VENDOR_ID = _ab_vendor_idROLE_VENDOR = vendor
2. Asset system
The front-end asset registry lives in includes/class-assets.php.
Responsibilities:
- registers cart, archive, vendor selector, buybox, profile, and APF bridge scripts
- registers vendor selector, buybox, and cart styles
- conditionally enqueues assets on product, cart, and archive-like views
- injects a shared
window.APC_CART_VENDOR_CFGpayload for front-end consumers
Notable registered handles include:
apc-cart-vendor-blocksapc-cart-vendor-singleapc-cart-vendor-archivesapc-vendor-selectorab-vendor-profileab-wcds-vendor-buyboxab-wcds-apf-vendor-bridge
3. Vendor resolution and offer storage
Vendor offer and resolution logic is split across:
includes/Vendors/VendorResolver.phpincludes/Vendors/VendorPricingOffers.php
VendorResolver handles fulfillment-oriented vendor eligibility and vendor selection rules.
Responsibilities:
- reads canonical fulfillment offers from
_apc_vendor_offers - falls back from variations to parent products
- supports legacy single-vendor meta synthesis
- treats unpi
ed cart items as Store by default
- resolves vendor origin data from vendor post meta
VendorPricingOffers handles pricing-offer persistence.
Responsibilities:
- stores vendor pricing offers in
_ab_vendor_pricing_offers - normalizes unit pricing, tiers, lead days, status, and source metadata
- supports per-vendor upserts for products and variations
- supports bulk upsert workflows for CSV/API ingestion
This separation is important:
_apc_vendor_offersis the canonical eligibility and storefront-offer surface_ab_vendor_pricing_offersis the vendor pricing-offer storage used by vendor ingestion/admin workflows
4. Cart and Store API vendor persistence
Cart vendor persistence is implemented across:
includes/Frontend/Cart/Cart_Vendor_Switcher.phpincludes/Frontend/Cart/Cart_Vendor_Store_Extension.phpincludes/Frontend/Cart/Cart_Vendor_REST.php
Cart_Vendor_Switcher handles classic cart UI.
Responsibilities:
- renders a vendor selector per cart line item
- writes selected vendor IDs to
apc_vendor_idcart item data - restores the value into the cart session on update
Cart_Vendor_Store_Extension handles the Store API and Blocks path.
Responsibilities:
- captures vendor IDs from Store API add-to-cart payloads
- persists vendor IDs under
apc_vendor_id - exposes vendor info under
extensions.apcin Store API item responses - hydrates offers from
_apc_vendor_offers - backstops cart responses when downstream extensions fail to inject data
Important namespace split:
- read namespace:
apc - write namespace:
ab-wcds-vendor
Note: Store API hook registration is delegated to Athenian Platform Core's cart extension bridge. This class owns the logic, not the global hook registration.
5. Storefront and vendor-facing shortcodes
The shortcode surface lives under includes/Frontend/Shortcodes.
Implemented shortcode families in this snapshot include:
Vendor_Selector_ShortcodeVendor_Dashboard_ShortcodeVendor_Portal_ShortcodeVendor_Info_ShortcodeVendor_Offers_Summary_ShortcodeVendor_Buybox_ShortcodeVendor_Onboard_Shortcode
The most important front-end surfaces are:
#### Vendor buybox
includes/Frontend/Shortcodes/Vendor_Buybox_Shortcode.php
Responsibilities:
- renders a store-first plus vendor-offer buybox
- compares native store pricing with competing vendor offers
- supports variation-aware and quantity-aware offer display
- can bridge into APF through
ath/apc/vendor_buybox_html - reads offers from
_apc_vendor_offers
#### Vendor portal
includes/Frontend/Shortcodes/Vendor_Portal_Shortcode.php
Responsibilities:
- renders the vendor portal and dashboard UI
- adds a Woo My Account
vendorendpoint for linked vendor users - gates access through vendor linkage, admin capabilities, or vendor role
- exposes portal-specific REST routes under
ath-dropship/v1 - lets vendor users manage their offer data and view scoped order context
#### Vendor onboarding
includes/Frontend/Shortcodes/Vendor_Onboard_Shortcode.php
Responsibilities:
- renders the public onboarding UX
- works with the onboarding REST controller to create pending vendor applications
6. Shipping package splitting and rate overrides
Shipping logic lives in:
includes/Shipping/Package_Splitter.phpincludes/Shipping/Rate_Overrides.php
Package_Splitter is one of the core operational modules.
Responsibilities:
- splits WooCommerce shipping packages by logical vendor group
- defaults to Store when no vendor is explicitly pi
ed
- supports optional fallback to product-level vendor mapping through filters
- populates package
originandab_vendor_meta
> Source excerpt shortened for the baseline web reference; the linked repository remains authoritative for the complete document.
Install
- Plugin file: athenian-wc-dropship/athenian-wc-dropship.php
- Live installed version: 0.3.31
- Canonical repository version: 0.4.1
- Version drift requires review before publication: live 0.3.31, canonical 0.4.1.
- Product ID: 90060
Configuration
- CHANGELOG.md u2014 Changelog; 0.4.1
- README.md u2014 Athenian WooCommerce Dropship; Requirements; Runtime surface; Security and operational boundaries; Development checks
docs/athenian-platform-marketing.md u2014 WC Dropship - Marketing Platform Brief; Product Positioning; Platform Value; Primary Audiences; Key Capabilities to Promote; Ecosystem Fit; Suggested Product Page Short Description; Suggested Product Page Long Description
docs/athenian-platform-technical.md u2014 WC Dropship - Technical Platform Brief; Plugin Identity; Technical Purpose; Source Inputs Reviewed; Source-Derived Signals; Implementation Surfaces; WordPress and WooCommerce Touchpoints; Data and Configuration
docs/developer/athenian-wc-dropship-developer-documentation.md u2014 Athenian WooCommerce Dropship Developer Documentation; Overview; High-Level Architecture; Bootstrap Sequence; Core constants and autoloading; WooCommerce feature declarations; Activation and rewrite behavior; Hard dependency on Athenian Platform Core
docs/marketing/athenian-wc-dropship-marketing-document.md u2014 Athenian WooCommerce Dropship Marketing Draft; Working positioning; Executive summary; Core marketing message; The problem Athenian WooCommerce Dropship solves; What Athenian WooCommerce Dropship does; 1. Builds a usable vendor network inside WooCommerce; 2. Makes vendor offers actionable at the product level
docs/marketing/athenian-wc-dropship-platform-overview.md u2014 Athenian WooCommerce Dropship Marketing Overview; Positioning Statement; Executive Summary; What Athenian WooCommerce Dropship Brings To The Platform; Ecosystem Narrative; Athenian Platform Core; Athenian Print Forge; Athenian Product Add-ons
docs/technical-marketing.md u2014 Athenian WooCommerce Dropship u2014 Technical & Marketing Overview; 1. Executive Summary; 2. Marketing Positioning; Short Positioning Statement; One-Sentence Description; Website Description; Sales-Focused Description; 3. Core Value Proposition
Usage
Athenian WooCommerce Dropship Developer Documentatio
Overview
Athenian WooCommerce Dropship is a WooCommerce vendor-orchestration plug-in that adds vendor onboarding, vendor portals, competitive vendor offer handling, cart and Store API vendor selection, shipping package splitting, purchase-order generation, vendor email dispatch, shipment-label workflows, and payout-ready settlement snapshots.
In this repository snapshot, the plug-in acts as the supply-side execution layer of the broader Athenian Platform and is designed to work with:
- WooCommerce for cart, checkout, orders, shipping, and order-item storage
- Athenian Platform Core (required) for the canonical Vendor CPT and shared bridge patterns
- optional ACF field groups for vendor and PO data entry
- optional Athenian Print Forge and Product Add-ons order metadata for artwork, proofing, and production-file handoff
High-Level Architecture
The main bootstrap file is
athenian-wc-dropship.php. It defines constants, registers the namespace autoloader, declares WooCommerce feature compatibility, checks for WooCommerce and Athenian Platform Core, and then defers all runtime bootstrapping toAthenianWCDropshipPlugin.At a high level, the plug-in is composed of seven layers:
- Bootstrap and compatibility declarations
- Vendor and storefront runtime wiring
- Cart and Store API vendor persistence
- Shipping package splitting and rate a
otatio
- Purchase-order generation and vendor communications
- Shipment and payout workflows
- Admin, vendor onboarding, and portal surfaces
Bootstrap Sequence
Core constants and autoloading
The root plug-in file defines:
AB_WCDS_PATHAB_WCDS_URLAB_WCDS_VERSIONAB_WCDS_DEBUG
It also registers a PSR-4-ish autoloader for classes under
AthenianWCDropship*, with a dashed-file fallback for class files such asclass-vendor-portal-shortcode.php.WooCommerce feature declarations
On
before_woocommerce_init, the plug-in declares compatibility with:custom_order_tablescart_checkout_blocksnew_product_editor
Activation and rewrite behavior
includes/Setup.phphandles basic lifecycle work:- activation sets
_ab_wcds_needs_flush=1 initloads the text domai
initflushes rewrites once after activation when needed
The main plug-in also registers the Woo My Account
vendorendpoint during runtime.Hard dependency on Athenian Platform Core
Plugin::__construct()exits early with an admin notice ifAPC_PATHis not defined. In practice, this plug-in expects Athenian Platform Core to provide the canonical Vendor CPT and shared platform wiring.Primary boot path
Once WooCommerce is available,
Plugin::instance()wires the major runtime modules:- assets
- setup and admin classes
- vendor role and vendor-user linking helpers
- shortcodes and vendor profile routes
- APF vendor buybox integratio
- PO subsystem
- shipping, email, PDF, and shipment label services
- REST controllers
Main Runtime Modules
1. Root orchestrator
The main runtime orchestrator lives in
includes/Plugin.php.Responsibilities:
- verifies Platform Core is present
- initializes feature modules
- exposes canonical meta keys such as
_apc_vendor_eligibleand_apc_vendor_offers - manages vendor role creatio
- manages vendor post to user and user to vendor linking
- renders APF vendor buybox fallback HTML through the
ath/apc/vendor_buybox_htmlfilter
Important constants in this class include:
META_VENDOR_ELIGIBLE = _apc_vendor_eligibleMETA_VENDOR_OFFERS = _apc_vendor_offersMETA_VENDOR_USER_ID = _ab_vendor_user_idMETA_USER_VENDOR_ID = _ab_vendor_idROLE_VENDOR = vendor
2. Asset system
The front-end asset registry lives in
includes/class-assets.php.Responsibilities:
- registers cart, archive, vendor selector, buybox, profile, and APF bridge scripts
- registers vendor selector, buybox, and cart styles
- conditionally enqueues assets on product, cart, and archive-like views
- injects a shared
window.APC_CART_VENDOR_CFGpayload for front-end consumers
Notable registered handles include:
apc-cart-vendor-blocksapc-cart-vendor-singleapc-cart-vendor-archivesapc-vendor-selectorab-vendor-profileab-wcds-vendor-buyboxab-wcds-apf-vendor-bridge
3. Vendor resolution and offer storage
Vendor offer and resolution logic is split across:
includes/Vendors/VendorResolver.phpincludes/Vendors/VendorPricingOffers.php
VendorResolverhandles fulfillment-oriented vendor eligibility and vendor selection rules.Responsibilities:
- reads canonical fulfillment offers from
_apc_vendor_offers - falls back from variations to parent products
- supports legacy single-vendor meta synthesis
- treats unpi
ed cart items as Store by default
- resolves vendor origin data from vendor post meta
VendorPricingOffershandles pricing-offer persistence.Responsibilities:
- stores vendor prici
n[Excerpt truncated for the initial reference draft.]
Shortcodes
- ab_vendor_buybox u2014 includes/Frontend/Shortcodes/Vendor_Buybox_Shortcode.php
- ab_vendor_profile u2014 includes/Frontend/Shortcodes/Vendor_Profile_Shortcode.php
- ab_vendor_onboard u2014 includes/Frontend/Shortcodes/Vendor_Onboard_Shortcode.php
- ab_vendor_info u2014 includes/Frontend/Shortcodes/Vendor_Info_Shortcode.php
- ab_vendor_offers_summary u2014 includes/Frontend/Shortcodes/Vendor_Offers_Summary_Shortcode.php
REST Endpoints
- apc/v1/cart/vendor u2014 includes/Frontend/Cart/Cart_Vendor_REST.php
Hooks
- apc/vendor_cpt_slug u2014 includes/Vendors/VendorResolver.php
- ab_wcds/vendor_id_for_user u2014 includes/Vendors/VendorPricingOffers.php
- init u2014 includes/Vendors/Vendor_Reviews.php
- add_meta_boxes u2014 includes/Vendors/Vendor_Reviews.php
- save_post_ u2014 includes/Vendors/Vendor_Reviews.php
- manage_ u2014 includes/Vendors/Vendor_Reviews.php
- manage_ u2014 includes/Vendors/Vendor_Reviews.php
- transition_post_status u2014 includes/Vendors/Vendor_Reviews.php
- before_delete_post u2014 includes/Vendors/Vendor_Reviews.php
- deleted_post u2014 includes/Vendors/Vendor_Reviews.php
- apc/vendor_cpt_slug u2014 includes/Vendors/Vendor_Reviews.php
- apc/vendor_cpt_slug u2014 includes/Vendors/Api_Integration.php
- init u2014 includes/Vendors/VendorOfferGeoIndex.php
- added_post_meta u2014 includes/Vendors/VendorOfferGeoIndex.php
- updated_post_meta u2014 includes/Vendors/VendorOfferGeoIndex.php
- deleted_post_meta u2014 includes/Vendors/VendorOfferGeoIndex.php
- save_post_product u2014 includes/Vendors/VendorOfferGeoIndex.php
- save_post_product_variation u2014 includes/Vendors/VendorOfferGeoIndex.php
- save_post_ u2014 includes/Vendors/VendorOfferGeoIndex.php
- wp_trash_post u2014 includes/Vendors/VendorOfferGeoIndex.php
- untrash_post u2014 includes/Vendors/VendorOfferGeoIndex.php
- before_delete_post u2014 includes/Vendors/VendorOfferGeoIndex.php
- wp_trash_post u2014 includes/Vendors/Vendor_Offer_Lifecycle.php
- untrash_post u2014 includes/Vendors/Vendor_Offer_Lifecycle.php
Data Model
---nplugin_slug: athenian-wc-dropshipnplugin_name: athenian-wc-dropshipndoc_type: technicalnsource_batch: temp-athenian-plugin-markdown-sources-20260701-094754nsource_priority: updated-overlay-plus-reponprimary_category_id: cat-marketplace-cha
elsncategory_ids: 'cat-orders-fulfillment;cat-marketplace-cha
els'ntag_ids: 'tag-wordpress-plugin;tag-orders;tag-operations;tag-shipping;tag-logistics;tag-fulfillment;tag-dropship;tag-marketplace;tag-co
ectors'nsite_nav_section_ids: 'nav-ecommerce-marketplaces'nsource_plugin_path: 'C:UsersscottDocumentsGitHubathenian-wc-dropship'ngenerated_at: 2026-07-01T15:51:27Z ---
WC Dropship - Technical Platform Brief
Plugin Identity
- Plugin slug:
athenian-wc-dropship - Plugin folder:
C:UsersscottDocumentsGitHubathenian-wc-dropship - Plugin header file(s):
athenian-wc-dropship.php - Header name: Athenian WooCommerce Dropship
- Version: 0.4.1
- Primary category: Orders, Fulfillment & Logistics
- Category IDs: `cat-orders-fulfillment;cat-marketplace-cha
els`
- Tag IDs: `tag-wordpress-plugin;tag-orders;tag-operations;tag-shipping;tag-logistics;tag-fulfillment;tag-dropship;tag-marketplace;tag-co
ectors`
- Source priority:
updated-overlay-plus-repo
Technical Purpose
Vendors, dropship flows, vendor portal UI/REST. Works with MU Core Vendors & PriceDelegate.
Within the Athenian Platform ecosystem, this plugin is documented as part of the following operating context:
- cat-orders-fulfillment: Order operations, fulfillment workflows, shipping carriers, dropship, returns, cancellations, and customer service resolution.
- cat-marketplace-cha
els: Marketplace operations, external cha
el integrations, supplier/manufacturer workflows, Google Sheets/GraphQL bridges, and multi-vendor commerce.
- nav-ecommerce-marketplaces: Commerce, marketplace, catalog, orders, shipping, cha
els, and WooCommerce products.
Source Inputs Reviewed
- athenianbrands-updated-markdowns: athenian-wc-dropship-technical-marketing.md
- plugin-repo-markdown: docsdeveloperathenian-wc-dropship-developer-documentation.md
- plugin-repo-markdown: docsmarketingathenian-wc-dropship-marketing-document.md
- plugin-repo-markdown: docsmarketingathenian-wc-dropship-platform-overview.md
- Source character count: 84349
- PHP files sca
ed: 66
Source-Derived Signals
Key source headings and repeated concepts identified from the current Markdown corpus:
- Athenian WooCommerce Dropship u2014 Technical & Marketing Overview
- 1. Executive Summary
- 2. Marketing Positioning
- Short Positioning Statement
- One-Sentence Descriptio
- Website Descriptio
- Sales-Focused Descriptio
- 3. Core Value Propositio
- Key Benefits
- 4. Best-Fit Use Cases
- 5. Customer, Vendor, and Admin Workflow
- Customer-Facing Flow
Representative source context:
- Plugin: Athenian WooCommerce Dropship Slug / package:
athenian-wc-dropshipVersion inspected:0.4.1Author: Scott Mays | Athenian Brands Text domain:ab-wc-dropshipPrimary platform: WordPress + WooCommerce Requires: PHP 8.0+, WordPress 6.2+, WooCommerce 7.1+ **WooCommerce compatibili... - Athenian WooCommerce Dropship is the vendor orchestration and fulfillment-routing layer of the Athenian Platform for WooCommerce. It extends WooCommerce beyond standard store-owned fulfillment by adding vendor onboarding, vendor account linking, product and variation-level vendor offers, storefront vendor selection, c...
- In a conventional WooCommerce store, an order is captured as one transaction, but vendor fulfillment often becomes a fragmented back-office process involving spreadsheets, emails, manually generated purchase orders, external shipping tools, and disco
ected payout calculations. This plugin closes that operational gap...
- The result is a commerce workflow where a customer can select or be routed to a vendor, that vendor choice is preserved through cart and checkout, the order can be split into vendor-specific fulfillment packages, purchase orders can be generated automatically, production files and custom order metadata can be carried...
- Athenian WooCommerce Dropship turns WooCommerce into a vendor-aware fulfillment platform with onboarding, vendor offers, cart routing, purchase orders, shipping labels, shipment confirmation, and payout-ready settlement snapshots.
Implementation Surfaces
Main PHP files:
- athenian-wc-dropship.php
Namespaces and classes:
- AthenianWCDropship
- AthenianWCDropshipAPI
- AthenianWCDropshipAdmi
- AthenianWCDropshipCompat
- AthenianWCDropshipFrontend
- AthenianWCDropshipFrontendCart
- AthenianWCDropshipFrontendShortcodes
- AthenianWCDropshipOrders
- AthenianWCDropshipPO
- AthenianWCDropshipPayout
- AthenianWCDropshipShipping
- AthenianWCDropshipUtil
- AthenianWCDropshipVendors
- missing
- not
- Assets
- Plugi
- Setup
- Vendor_Onboard_REST_Controller
- ACF_Fields
- Dashboard_Vendor_Stats
- Screen_Tidy
- Settings
- Vendor_API_Integratio
- Vendo
[Excerpt truncated for the initial reference draft.]
- Plugin slug:
API Reference
- Manifest hash: 1c23868cf9bf4b8aecb3595b6dac849539fea1d6
Sca
ed file count: 102
- Canonical repository commit: 3f34d507eb7ad76634d7d1b48bd7289bd1d08dde
Sca
er mode: installed plugin analyzer
Troubleshooting
- This document remains unpublished until the reference material and live behavior are manually verified.
- Version drift requires review before publication: live 0.3.31, canonical 0.4.1.
- The installed-plugin analyzer was exercised for this regular plugin.
FAQ
Is this reference published?
No. It is a draft for manual verification and enrichment.
Which source should reviewers treat as authoritative?
The pi
ed repository commit is the canonical source reference; the live installation is the deployed-behavior reference. Any difference is recorded as a review item.
Changelog
Changelog
0.4.1
- Established the clean repository foundation for the current vendor andn dropship runtime.
- Added repository contracts, release metadata, deterministic packaging, andn CI checks.
- Excluded generated browser sessions, screenshots, ZIP archives, and localn output from the source repository.
- Disabled the optional debug flag by default in the clean foundation.