← CC-Analysis

Auction-Pipeline Outbound — Integration Spec

The real marketplace feeds and auction-management software estate/auction sellers use — import formats, field rules, image conventions, and a TroveSnap adapter design. Researched 2026-06-17.

Fills the gap flagged in the pressure-test: the plan exports a generic auction CSV (buildAuctionExportCsv), but sellers live in specific marketplace feeds. All targets are Auth + connector gated (phase 2); file-based exports can ship before the API/two-way integrations. Specs are reported from vendor docs and should be re-verified before building — the LiveAuctioneers guide sampled here is dated (V3.3, 2018).

Why generic CSV isn't enough

There is no universal interchange format — each marketplace has its own template, field constraints, and image rules. That fragmentation is exactly the pain. The TroveSnap move: normalize once into the canonical record, emit a per-target package (template + lot-numbered images) as a reviewed draft, never auto-posted — the candidate-style outbound mirror of the ingestion contract.

Target platforms & how each ingests

PlatformIngest methodNotes
LiveAuctioneersSpreadsheet (XLSX → save as CSV / tab) + images via FTP / hosted URLStrict field rules (below). Images named by lot number by default. Auction software (Auction Flex, RFC, BidMaster) can export CSV for direct upload.
ProxibidBulk Loader: Excel/CSV with column mappingMulti-image naming 1-1, 1-2 (lot-image). Wavebid has a direct two-way integration.
Invaluable (+ AuctionZip + private-label)Catalog Upload API for auction-software partnersNot a raw consignor CSV — reached via partner API or via Auction Flex / Wavebid.
Auction Flex → HiBidSpreadsheet import into Auction Flex; native one-click upload to HiBidLot numbers present → into an auction; absent → inventory. Auction Flex is the dominant live-auction mgmt app.
Wavebid"Universal Export"; two-way API integrationsDirect export + sale-results pull-back for Proxibid and Invaluable/AuctionZip; LiveAuctioneers manual.

LiveAuctioneers field spec (the reference template)

Mandatory columns: LotNum · Title · Description · LowEst · HighEst · StartPrice

Optional: Condition · Consignor (internal) · ImageFile.1ImageFile.20 · Buy Now Price · Exclude From Buy Now (0/1) · Reserve Price · Height/Width/Depth + Dimension Unit (in/ft/cm) · Weight + Weight Unit (oz/lb/g/kg) · Quantity.

Images — named by lot number by default (24.jpg, 24-2.jpg) OR listed in ImageFile.N (full filename incl. .jpg, case-sensitive), or a hosted URL. Save as CSV/tab to preserve special characters.

TroveSnap field mapping (canonical → LiveAuctioneers)

TroveSnap canonical→ LiveAuctioneersTransform / validation
item titleTitletruncate / warn at 49 chars
AI / edited listing copyDescriptionHTML-safe, strip links, <br> newlines
internal low/high guidanceLowEst / HighEststrip $; enforce low ≤ high
suggested starting bid (~40% high)StartPricereuse suggestStartingBid; ≤ low
reserve (60% when ≥ $500)Reserve Pricereuse existing disposition logic
conditionConditionpass-through
seller / consignorConsignorinternal only
item photoslot-numbered files / ImageFile.Nemit image bundle named by lot
dimensions / weightHeight/Width/Depth + unitsunit normalize
lot quantityQuantitywhole-lot price only

Most of this already exists in troveDisposition.ts (buildAuctionExportCsv, suggestStartingBid) — the work is generalizing it from one CSV to a per-target export profile.

Recommended adapter design

  1. Export profiles — one per target (liveauctioneers, proxibid, auctionflex, hibid, invaluable, wavebid, generic). A profile = column map + field validators + image-naming rule.
  2. Image-bundle emitter — the structural piece the current CSV export lacks: a folder/zip of images named by lot number (and the 1-2/24-2 sequence), or filled ImageFile.N.
  3. Validation surfaced in review — warn before download on title > 49, missing/mis-ordered estimates, currency symbols, links in description, missing lot numbers. Same review-gate spirit as the ingestion contract.
  4. Reviewed draft only — produces a downloadable package; never auto-posts.
  5. Phasing within phase 2:
    • 2a — file exports (earlier): LiveAuctioneers / Proxibid / Auction Flex spreadsheet + lot-numbered image bundle. The file needs no third-party Auth.
    • 2b — API + two-way (needs Auth/connectors): Invaluable Catalog Upload API; Wavebid/Proxibid/Invaluable sale-results pull-back → inventory_status_events → recovered-revenue analytics. LiveAuctioneers results remain manual import.

Settlement / results back (closing the loop)

The inbound half: pull post-sale results (sold / passed / hammer price) from Proxibid, Invaluable/AuctionZip (direct), or manual for LiveAuctioneers, into the existing reconciliation path (inventory_status_events, sold price) so recovered-revenue and disposition-outcome analytics reflect actual auction results. Consignor-settlement reports are a later, finance-side extension.

Sources

Reported from vendor docs; re-verify current templates, field limits, and image rules with each platform before building an adapter.