The four connections
Each one exists because a real operation already had the other end of it. None of them is a bridge to a second system of record — the operational truth stays in one place, and these connections move specific, bounded things in and out of it.
- QuickBooks Online — outboundPosted AR invoices and receipts, AP bills and payments, plus the customers, vendors and items they depend on, pushed into QuickBooks after the accounting checks in AERONEXUM are satisfied.
- eBay — outboundA reviewed listing prepared from a specific stock unit, published to eBay US on explicit approval. Preparation and preview happen entirely inside AERONEXUM.
- PartsBase — inboundReal-time part search and availability against the PartsBase network, plus RFQs that arrive by email and are parsed into the system rather than re-keyed.
- ShipStation — bothAddress validation, rate shopping, label purchase, void, and tracking that comes back on a webhook instead of someone refreshing a carrier site.
QuickBooks Online
The AERONEXUM QuickBooks connector is an approved Intuit application, listed in Intuit's system as the AERONEXUM Connector. It runs one way: AERONEXUM is where the commercial and operational record lives, and QuickBooks is where the books live. Nothing in the integration tries to blur that.
What crosses the boundary is the set of documents accounting actually needs — AR invoices, AR receipts, AP bills and AP payments — along with the customers, vendors and items they reference. Account, customer, vendor and item mapping is explicit, set up once in an admin panel with auto-match suggestions for the obvious pairs and a coverage view for what is still unmapped. Nothing syncs against a guess.
The parts that matter in practice are the unglamorous ones. Every sync run is recorded with its own detail view, so a question about a figure in QuickBooks can be traced back to the run that put it there. Posting is idempotent — a retried or duplicated run checks for the existing reference before it creates anything, so a dropped connection cannot produce a second invoice. Voids and reversals propagate: void an AR invoice in AERONEXUM and it voids in QuickBooks. And a QuickBooks failure never blocks the operation. The local document posts, the row is flagged as failed, and it waits to be retried.
The ledger entry is created in AERONEXUM when the accounting checks pass, and then mirrored into QuickBooks. That ordering is the whole design. It means the operational system can always explain a financial entry back to the shipment, repair or exchange that produced it — which is the thing a re-keyed ledger can never do. The flow is drawn out in full on quote to general ledger.
eBay listings
Surplus moves slowly when listing it is somebody's least favourite job. The eBay integration exists to remove the re-keying: a listing is prepared from a part and a specific stock unit, so the part number, manufacturer and condition come from inventory rather than from a spreadsheet and a careful copy-paste.
From there it is a normal editorial pass — title, price, quantity, condition observations, description, item specifics, documentation statement. Photos can be taken on a phone through a QR-code upload session and attached to the stock unit itself, which means they are available to everything else that needs them later. A preview renders the buyer-facing gallery and presentation in both desktop and mobile layouts before anything is published. Publishing requires explicit approval of that specific reviewed listing. Current scope is eBay US, fixed price, in USD.
What is deliberately not copied into a draft: internal cost, stock comments, owner details and part notes. Serial numbers appear in the buyer preview only if someone explicitly chooses to include them.
Posting a unit to eBay does not reserve it. It stays available to every other channel — a direct customer, a marketplace RFQ, a counter sale — exactly as it was before the listing went up. What commits the stock is a Sales Order created in AERONEXUM. This is intentional: a listing is an offer, not a sale, and a trader who cannot sell a unit through a faster channel while it sits on eBay is worse off than before. The trade-off is real and worth stating plainly — somebody has to end a listing once the unit is gone.
PartsBase
PartsBase is a demand-and-sourcing connection, in use by AERONEXUM customers today, and it runs inbound. Part searches and availability lookups execute against the PartsBase network in real time, from inside the system where the resulting quote will be built — rather than in a second browser tab whose results then get typed somewhere.
The more valuable half is quieter. RFQs that arrive by email are parsed into the system automatically, which matters because an inbox is where requests go to die. A broker's morning triage is a real activity with real economics — it is described at length here — and the difference between a request that arrives as structured demand and one that arrives as unread mail is most of whether it gets answered first.
ShipStation
Shipping is where a clean operation most often goes wrong at the last step, and usually for mundane reasons: an address that was never quite right, a label bought at the wrong service level, tracking nobody chased. The ShipStation connection is aimed squarely at those.
- Addresses checked before money is spentA saved address is validated against the carrier's own data, with the suggested correction offered alongside the option to keep it as entered when the operator knows better.
- Rates compared, then boughtLive rates across the carriers on the account, and the label purchased against the chosen one as PDF or as ZPL for a thermal printer.
- Blind shippingWhen a package ships out of a repair station or a third-party location, the label can carry your company's name rather than the location's. For anyone shipping on behalf of a customer, this is not cosmetic.
- Tracking that updates itselfCarrier scans arrive on a webhook and land against the shipment. Labels can also be voided, and tracking refreshed on demand when something looks stale.
What these integrations do not do
Integration pages tend to imply that once two systems are connected, everything flows automatically in both directions. These do not, and the gaps are worth knowing before anyone plans around them.
- They do not replace your accounting systemPeriod close, revenue recognition, inventory valuation and tax stay in QuickBooks. The connector feeds it; it does not compete with it.
- An eBay listing does not hold stockNo reservation, no decrement. The sale becomes real in AERONEXUM when a Sales Order is created against the unit.
- PartsBase is sourcing in, not listing outSearch, availability and inbound RFQs. AERONEXUM does not publish your inventory to the PartsBase network.
- None of them is a parts marketplaceAERONEXUM does not source parts on your behalf or introduce you to counterparties. It connects to the places where that already happens.
Why connect instead of replace
The alternative approach is familiar enough: absorb everything, become the accounting system too, build a marketplace, print the labels. It demonstrates well. It also asks a business to abandon systems that work, retrain the people who run them, and accept a weaker version of each one for a few years in exchange for a single login.
The position here is narrower on purpose. AERONEXUM holds the operational and commercial record — what was promised, what physically moved, what condition it was in, what it is worth, who owes what — because that is the layer where fragmentation actually costs money. For the things that already have a good home, it connects. The accountant keeps QuickBooks and stops re-keying invoices. The shipping desk keeps its carrier accounts and stops re-typing addresses. Surplus reaches eBay without a second inventory list. RFQs arrive as work rather than as mail.
Which is the same ambition as everywhere else on this site: fewer places for the truth to drift apart, and less of the day spent moving it by hand.