AP Fusion Integration – Feature & Process Guide

AP Fusion is a REST-based order and fulfilment platform built on the open-source Spree Commerce framework. It's most commonly used by sellers of automotive and aftermarket parts, though the integration works the same way for any AP Fusion account. Pentagon Connect connects to each shop individually using a Client ID and Client Secret issued by AP Fusion.

Once connected, Pentagon Connect keeps price and stock in sync and pulls orders in automatically, pushing shipping confirmations back to AP Fusion once an order is ready to go. There is no product-creation or listing-management capability in this integration today.

Quick Reference

Product Management

Pricing & Stock

Orders & Fulfilment

Refunds, Returns, Cancellations & Claims

Pricing & Stock Sync

Price updates are sent per SKU and carry just two values: the listing title and the price. AP Fusion only accepts a single price per SKU — there's no separate RRP, compare-at, or strike-through price field, so discount/was-price display isn't something this integration can drive.

Stock updates are also sent per SKU, against a single warehouse location that's configured once at the channel level (covering every SKU on that channel). There's no per-SKU or multi-warehouse stock split. If that location hasn't been configured for a channel, stock updates fail with a hard error rather than silently being skipped, so a channel with unexpected stock-sync failures should be checked for a missing location setting first.

Order Management

Getting orders

Orders are pulled from AP Fusion automatically: Pentagon Connect first retrieves a page of order summaries, then fetches each order individually for full detail. On a shop's first sync, orders are pulled from the last 90 days; after that, each sync overlaps the previous one by 90 minutes to avoid missing anything. Anything older than 90 days at first connection, or a very old order that's edited outside that rolling overlap window, can be missed.

AP Fusion tracks order progress through several of its own internal states, and a few of those states don't map one-to-one onto Pentagon Connect's order statuses. In particular, several distinct "in progress" states on the AP Fusion side all show up as the same "Ready for Shipping" status in Pentagon Connect, so support can't distinguish those sub-states from the Pentagon Connect order status alone — that's expected behaviour, not a sync fault.

Order information we store

For each order, Pentagon Connect currently stores:

• Marketplace order ID and order number
• Order total and shipping cost
• Buyer's user ID and email address
• Order created and last-updated timestamps
• Any order note / special instructions text

Billing and shipping addresses, individual line-item/product detail, tax breakdown, and payment state are present in AP Fusion's own order data but are not currently captured by this integration — see Known Limitations below.

Shipping orders

An order can be shipped once it's in "Ready for Shipping" status with its shipment still pending. AP Fusion only accepts full-order shipments — there's no partial/split shipment support, so an order can't be shipped in multiple parcels through this integration.

Courier resolution uses a three-step fallback when a tracking update is sent: first, a mapping table that translates our carrier names onto AP Fusion's own carrier codes; if there's no mapping for that carrier, a channel-level default carrier (if one is configured); if neither applies, the shipment update fails and is flagged as an error until a mapping or default is put in place. AP Fusion only accepts carrier codes from its own fixed list (see below) — an unrecognised carrier name won't work.

Carriers Supported

AP Fusion only accepts tracking updates for carriers on its own fixed list — an unlisted carrier can't be used unless it's mapped to one of these or covered by the channel's default carrier. The list currently includes: An Post, APC Postal Logistics, Aramex, Australia Post, bpost, Canada Post, Canpar Courier, China Post, Chronopost France, Colissimo, DHL Express, DHL eCommerce US, DPD, EVRi, Fastway Australia, FedEx, FedEx Ground Economy, Hermesworld, Hong Kong Post, Japan Post, Landmark Global, Malaysia Post, Mondial Relay, onTrac, Quantium, Royal Mail, Correos Spain, StarTrack, Swiss Post, TNT, Toll Priority, United Parcel Service (UPS), UPS Mail Innovations, U.S. Postal Service, USPS (discounted), and Yodel.

Known Limitations

• No product creation, content updates, or deactivation — only price and stock can be updated on an existing product; there's no documented way to create, fully edit, or take down a listing through this integration.
• No cancellations, refunds, returns, or claims — none of this integration's source material covers these flows, so none of them are supported today.
• Only full-order shipments — AP Fusion has no partial/split shipment capability.
• One stock location per channel — stock is written to a single configured warehouse location; there's no per-SKU multi-warehouse split, and a missing location setting is a hard error blocking stock updates.
• No RRP/strike-through pricing — price sync sends a single price value only.
• Carrier codes are a fixed, closed list — a carrier not on AP Fusion's list can't be used unless mapped or covered by a default carrier; otherwise the shipment update fails.
• Order status can be ambiguous — several distinct AP Fusion order states collapse into the same "Ready for Shipping" status in Pentagon Connect.
• Limited order data capture — full billing/shipping addresses, line-item/product detail, tax breakdown, and payment state aren't currently stored, even though AP Fusion returns them.
• Order sync lookback window — a first-time sync only looks back 90 days, and later syncs use a 90-minute overlap, so very old or late-edited orders can be missed.

Source Materials

This guide was built from AP Fusion's technical integration specifications covering authentication, order retrieval, order shipment, and price/stock updates.