Athenian UPS Shipping Integration
Overview
Product overview
Shipping breaks down when checkout quotes, packaging assumptions, and label generation live in separate systems. Rates may be estimated with flat rules, package dimensions may be guessed manually, label creation may happen outside WooCommerce, and tracking data may never make it back into the order record. The result is margin leakage, operational rework, and a weaker customer experience.
Athenian UPS Integration solves that by making UPS a native part of WooCommerce order flow. It requests live UPS rates, builds package payloads from product weight and dimension data, retries intelligently when UPS rejects package assumptions, stores service and package metadata at checkout, and generates shipment labels tied back to the order after purchase.
Use cases
- UPS rates
- Shipping labels
- Tracking
- Fulfillment operations
Developer
Developer starting point
This baseline documents the UPS integration architecture. It does not claim that a carrier request, rate, label, tracking update, or shipment has been exercised.
What Athenian UPS Integration does
1. Brings live UPS rates into WooCommerce checkout
Athenian UPS Integration connects directly to UPS APIs to request real-time shipping rates during checkout. Merchants can:
- Shop available UPS services dynamically
- Restrict rates to selected UPS services
- Apply handling fees and percentage-based adjustments
- Control whether residential or commercial delivery assumptions are automatic or fixed
- Keep UPS rate logic inside WooCommerce shipping zones and instance settings
This gives merchants live carrier-backed pricing without abandoning WooCommerce's native shipping architecture.
2. Converts catalog data into shippable package logic
The plugin builds shipment packages from WooCommerce product data, including:
- Weight
- Length, width, and height
- Quantity
- Store unit settings
- Fallback values when product data is incomplete
It supports multiple packaging strategies:
- 3D box packing using merchant-defined box definitions
- Single combined package mode
- One-package-per-item mode
This matters because shipping accuracy depends on package construction, not just product totals.
3. Adds resilience when UPS rejects a shipment assumption
UPS rating can fail when package type or destination assumptions do not match what the API expects. Athenian UPS Integration is built to recover from those situations by:
- Retrying alternate UPS package type codes when enabled
- Falling back from service-shopping requests to per-service rating requests
- Re-evaluating residential versus commercial assumptions when needed
- Logging request and response summaries for debugging when merchants enable diagnostics
That resilience helps stores keep shipping options visible instead of silently failing during checkout.
4. Connects checkout shipping selections to fulfillment actions
When a shopper selects a UPS rate, the plugin captures and persists:
- UPS service code
- UPS package type code
- Packed shipment metadata
- Environment context used for the request
That data is written into the WooCommerce order context so the same shipping decision made at checkout can drive fulfillment and label creation later.
5. Generates UPS shipping labels from the order
After purchase, Athenian UPS Integration can generate UPS labels directly from WooCommerce order data. It:
- Builds shipment requests from order addresses and packed item data
- Creates UPS shipments through the UPS shipping API
- Stores tracking numbers and tracking URLs on the order
- Persists generated label PDFs to the WordPress uploads directory
- 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 operational shipping workflows
The plugin is not limited to a single order-screen action. It also integrates with Athenian shipment-management flows by:
- Registering UPS as a carrier in the Athenian shipment manager layer
- Exposing callbacks for label generation and previously generated label reads
- Supporting packed meta handoff for downstream shipping workflows
- Participating in purchase-order label generation where vendor or fulfillment routing requires it
That makes it useful as both a storefront shipping method and an operational shipping service inside the Athenian ecosystem.
Ecosystem integration story
WooCommerce
Athenian UPS Integration is implemented as a native WooCommerce shipping method. It uses shipping zones, instance settings, order actions, shipping-item metadata, logger support, and checkout hooks so merchants can manage UPS shipping inside the operating model WooCommerce already uses.
Athenian shipment workflows
The plugin extends beyond checkout rating by integrating with Athenian shipment-manager style flows and purchase-order label hooks. That makes it viable for stores that need shipping execution to continue after checkout, not stop at rate display.
Order and fulfillment continuity
Because selected service codes, package codes, package payloads, labels, and tracking identifiers are persisted on the order, shipping context stays available to admins, fulfillment processes, and later operational tooling.
Install
- Reviewed source folder: athenian-ups-integration
- Plugin version reviewed: 1.0.3
- Local source inventory: 14 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-ups-integration at baseline/devdocs-1.0.3-20261006e / abd01f2c2670d613494fb3bb2b10751554c6808d.
- WordPress and WooCommerce.
- UPS credentials, live rates, labels, tracking, carrier requests, and 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 it solves — see the linked technical reference excerpt.
- What Athenian UPS 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.
- Lean competitive positioning — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 0
- Static action/filter hooks detected in local PHP source: 22
- 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_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_sm_registered_carriers — includes/Plugin.php
- ath_ups_brand_assets — includes/Plugin.php
- before_woocommerce_init — includes/Plugin.php
- init — includes/Plugin.php
- plugins_loaded — athenian-ups-integration.php
- woocommerce_admin_field_ath_ups_brand_image — includes/Plugin.php
- woocommerce_admin_field_ath_ups_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_ups_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_ups_validate_credentials — includes/Plugin.php
Data Model
- What Athenian UPS Integration does — described in the local technical reference.
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 7572775675f067eca503769c75d2dc439db7de92067d6714af1c55cc22f0c6d9
- Repository URL: https://github.com/Athenian-Brands/athenian-ups-integration
- Repository reference: baseline/devdocs-1.0.3-20261006e
- Repository commit: abd01f2c2670d613494fb3bb2b10751554c6808d
Source files include: assets/js/admin-settings.js, athenian-ups-integration-icon.png, athenian-ups-integration.php, athenian-ups-integration.zip, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/athenian-ups-marketing-document.md, docs/technical-marketing.md, includes/Admin/Settings.php, includes/Labels/Manager.php, includes/Packing/Packer.php, includes/Plugin.php, includes/Shipping/Method.php, includes/UPS/Client.php
Troubleshooting
- This baseline documents the UPS 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.