Athenian FedEx Shipping Integration
Overview
Product overview
Shipping workflows become inefficient when rating, packaging, and label creation live in different systems. Checkout may rely on estimated shipping rules, package assumptions may be inconsistent, label generation may happen outside WooCommerce, and tracking data may never make it back to the order record. The result is avoidable margin loss, manual re-entry, and weaker fulfillment continuity.
Athenian FedEx Integration solves that by making FedEx a native part of WooCommerce order flow. It requests live FedEx rates, builds package payloads from product weight and dimension data, applies configurable rate controls, stores shipping metadata on the order, and generates shipment labels directly from order context.
Use cases
- Carrier rates
- Shipping labels
- Tracking
- Fulfillment
Developer
Developer starting point
This baseline documents the FedEx integration architecture. It does not claim that a carrier request, rate, label, tracking update, or shipment has been exercised.
What Athenian FedEx Integration does
1. Brings live FedEx rates into WooCommerce checkout
Athenian FedEx Integration connects directly to the FedEx REST API for real-time rating during checkout. Merchants can:
- Request all available FedEx services or only selected services
- Limit shopper-visible options to approved FedEx service levels
- Choose account or list rates
- Apply flat handling fees and percentage-based rate adjustments
- Return transit-time information with rates when desired
- Control residential-versus-business rating behavior
This keeps carrier-backed pricing inside WooCommerce's native shipping-method model.
2. Converts catalog data into shipment-ready package logic
The plugin builds package payloads from WooCommerce product data, including:
- Weight
- Length, width, and height
- Quantity
- Store measurement units
- Fallback values when product data is incomplete
It supports multiple packaging strategies:
- 3D box packing with merchant-defined box definitions
- Single combined package mode
- One-package-per-item mode
This matters because shipping accuracy depends on package construction, not just cart totals.
3. Gives merchants practical control over FedEx service behavior
FedEx rates are only useful if the merchant can shape how they are presented. Athenian FedEx Integration lets stores:
- Set checkout titles for the shipping method
- Define allowed FedEx services
- Choose FedEx packaging types
- Configure pickup type defaults
- Set environment-specific credentials for staging and production
- Validate FedEx OAuth connectivity from WooCommerce settings
That gives operations and implementation teams tighter control over shipping behavior without leaving the admin.
4. Connects checkout selections to order-level shipping context
When a shopper selects a FedEx rate, the plugin captures and persists:
- FedEx service type
- Service name
- Rate type
- Transit-time details
- Delivery date details
- Currency
- Packed package metadata
- Environment context
That data is stored on the WooCommerce order and shipping item so the selected shipping path remains available after checkout.
5. Generates FedEx shipping labels directly from the order
After purchase, Athenian FedEx Integration can generate FedEx labels from WooCommerce order data. It:
- Builds shipment requests from stored or derived package information
- Uses the selected checkout service when available
- Falls back to a configured default service when needed
- Creates FedEx shipments through the FedEx shipping API
- Stores tracking numbers and tracking URLs on the order
- Persists PDF label files to disk
- Supports admin-triggered label generation from WooCommerce order actions
This reduces manual handoff between checkout and fulfillment while keeping shipment records attached to the transaction.
6. Fits Athenian shipment workflows beyond the storefront
The plugin extends beyond basic checkout rating by integrating with Athenian shipping operations. It:
- Registers FedEx as a carrier in the Athenian shipment manager layer
- Exposes callbacks for label generation and label readback
- Provides packed shipment metadata to downstream workflow hooks
- Supports label generation for vendor shipment and purchase-order flows
- Respects origin context passed from operational workflows when available
That makes it useful as both a storefront shipping method and a fulfillment service inside the Athenian ecosystem.
Ecosystem integration story
WooCommerce
Athenian FedEx Integration is implemented as a native WooCommerce shipping method. It uses shipping zones, instance settings, WooCommerce order actions, shipping-item metadata, and WooCommerce logging so merchants can manage FedEx shipping within the workflows they already use.
Athenian shipment workflows
The plugin extends beyond checkout by integrating with Athenian shipment-manager style flows and vendor or purchase-order label generation hooks. That makes it viable for merchants that need shipping execution to continue after rate selection.
Order and fulfillment continuity
Because service selection, package metadata, labels, and tracking details are persisted on the order, shipping context stays available to admins and downstream fulfillment workflows.
Install
- Reviewed source folder: athenian-fedex-integration
- Plugin version reviewed: 3.4.1
- Local source inventory: 14 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-fedex-integration at baseline/devdocs-3.4.1-20261006e / c2c1cd6db7149f23f134759c6bef97817ac3cbe0.
- WordPress and WooCommerce.
- FedEx credentials, live rates, labels, tracking, carrier requests, and fulfillment 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 it solves — see the linked technical reference excerpt.
- What Athenian FedEx Integration 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: 23
- 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
- ab_wcds_build_shipping_label_pdf — includes/Plugin.php
- ab_wcds_generate_shipping_label — includes/Plugin.php
- ab_wcds_stub_label_packed_meta — includes/Plugin.php
- admin_enqueue_scripts — includes/Plugin.php
- admin_notices — includes/Plugin.php
- athenian_carrier_brand_assets — includes/Plugin.php
- ath_fedex_brand_assets — includes/Plugin.php
- ath_sm_registered_carriers — includes/Plugin.php
- before_woocommerce_init — includes/Plugin.php
- init — includes/Plugin.php
- plugins_loaded — athenian-fedex-integration.php
- woocommerce_admin_field_ath_fedex_brand_image — includes/Plugin.php
- woocommerce_admin_field_ath_fedex_validate — includes/Plugin.php
- woocommerce_checkout_create_order_shipping_item — includes/Plugin.php
- woocommerce_get_sections_shipping — includes/Plugin.php
- woocommerce_get_settings_shipping — includes/Plugin.php
- woocommerce_order_actions — includes/Plugin.php
- woocommerce_order_action_ath_fedex_generate_label — includes/Plugin.php
- woocommerce_shipping_init — includes/Plugin.php
- woocommerce_shipping_methods — includes/Plugin.php
- woocommerce_update_options_shipping_ — includes/Plugin.php
- woocommerce_update_options_shipping_ — includes/Shipping/Method.php
- wp_ajax_ath_fedex_validate_credentials — includes/Plugin.php
Data Model
- What Athenian FedEx Integration does — described in the local technical reference.
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 2f71b170a823ee4dd9932ad729c33ced76538a6e210d7a4e5d9aa09d2b89f516
- Repository URL: https://github.com/Athenian-Brands/athenian-fedex-integration
- Repository reference: baseline/devdocs-3.4.1-20261006e
- Repository commit: c2c1cd6db7149f23f134759c6bef97817ac3cbe0
Source files include: assets/js/admin-settings.js, athenian-fedex-integration-icon.png, athenian-fedex-integration.php, athenian-fedex-integration.zip, docs/athenian-fedex-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/technical-marketing.md, includes/Admin/Settings.php, includes/FedEx/Client.php, includes/Labels/Manager.php, includes/Packing/Packer.php, includes/Plugin.php, includes/Shipping/Method.php
Troubleshooting
- This baseline documents the FedEx integration architecture. It does not claim that a carrier request, rate, label, tracking update, or shipment 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.