Simple Commerce Australia Post Laravel Package

Technical Evaluation

Architecture fit mitydigital/simple-commerce-australia-post is a narrow adapter package: a Laravel service provider that registers an Australia Post shipping/fulfilment integration into Statamic's Simple Commerce addon. Architecturally it is low-footprint and appropriate for the job — it should own API authentication, payload construction, rate/consignment calls, and mapping responses back into Simple Commerce's shipping method contract. The main architectural concern is coupling: it depends on Simple Commerce internals, so its stability is bounded by that upstream addon's release cadence, not just its own.

Integration feasibility Standard Laravel package mechanics apply: Composer require, publish config, supply Australia Post API credentials (account number, API key), and enable the shipping method in the Simple Commerce store config. Feasibility is high for a team already on Laravel + Statamic + Simple Commerce; it is not usable outside that stack. Evidence available for this review is limited to the 3.0.2 release note, so Laravel/PHP version constraints, test coverage, and API surface (rates only vs. labels/tracking) must be verified directly from the repo and composer.json.

Technical risk

• The 3.0.2 change — "Correct product reference" — is a behavioural bug fix on the outbound payload. Any fix to a product/parcel reference sent to Australia Post can change quoted rates or, worse, mean prior requests were submitted with the wrong product metadata. Orders quoted or consignments created under 3.0.1 should be reconciled rather than assumed correct.
• Release note integrity issue: the entry is titled 3.0.2 but links compare/3.0.1...3.1.0. Either the tag or the changelog is wrong. Confirm the actual published tag on Packagist before pinning; do not assume a patch-level bump.
• Single-maintainer package (@martyf) — bus-factor and long-term maintenance risk.
• Major version 3 implies a prior breaking baseline; confirm it aligns with your Simple Commerce major.

Key questions

1. What are the exact PHP, Laravel, Statamic, and Simple Commerce version constraints?
2. Is this release rate-quoting only, or does it also affect label generation, tracking, and postage product codes?
3. Will quoted rates change after upgrading — i.e., is this a silent pricing behaviour change?
4. Is the changelog/version mismatch a documentation error or an unreleased 3.1.0?
5. What is the automated test coverage, and is there a sandbox/test-mode path against Australia Post?
6. Does it support multiple box/parcel configurations and fallback behaviour when the API is unavailable?

Integration Approach

Stack fit Assumes Laravel (PHP 8.x), Statamic, and Simple Commerce v3+. The package should slot in as a shipping method with no schema changes; verify no migrations are shipped before assuming a clean install.

Migration path Treat 3.0.1 → 3.0.2 as a drop-in patch, but validate the tag first. Steps: pin the exact version in composer.json, composer update mitydigital/simple-commerce-australia-post, clear config and application caches, then re-run representative checkout quotes in staging against the Australia Post sandbox before touching production.

Compatibility Confirm that config keys, credential field names, and the shipping method class signature are unchanged. Check whether the "product reference" fix reads from store config or from the product model — if the latter, audit product data for missing/incorrect references that would now surface as errors instead of bad quotes.

Sequencing

1. Verify the real published version and diff 3.0.1...3.0.2 in the repo.
2. Stage the upgrade; capture rate outputs for a fixed basket of reference carts (domestic metro, regional, oversized, multi-item) on 3.0.1 vs 3.0.2.
3. Reconcile any orders or consignments created during the affected window.
4. Deploy to production in a low-traffic window with a manual shipping-rate fallback enabled.
5. Monitor quote success rate and rate-delta for 48 hours.

Operational Impact

Maintenance Low effort in steady state: periodic Composer bumps, credential rotation, and re-validation on each Simple Commerce major. Pin with a caret constraint but review each release; the 3.0.2/3.1.0 discrepancy argues against blind composer update.

Support Single-maintainer upstream. Budget for the possibility of forking or replacing with a direct Australia Post API client. Ensure at least one engineer on the team can read the package source and the AusPost API docs.

Scaling Rate calls occur per checkout session, so cost scales with cart traffic rather than order volume. Cache quotes per cart signature where Simple Commerce permits, and confirm timeout/retry behaviour so a slow AusPost response does not stall checkout.

Failure modes

• Australia Post API outage or credential expiry blocks checkout unless a fallback rate is configured — this is the highest-impact failure and should be handled explicitly.
• Malformed or missing product reference (the exact class of defect fixed here) producing rejected requests or silently wrong rates.
• Version skew between this package and Simple Commerce after an upstream upgrade.
• Silent rate changes after patch upgrades, caught only by parity testing.

Ramp-up Roughly half a day to a day for a Laravel developer familiar with Statamic: install, configure credentials, sandbox-test quotes, and document the fallback path. Add extra time for the first reconciliation exercise if 3.0.1 was already in production.