OFFICIAL EBAY ARCHITECTURE
From approved draft
to active listing.
LSTWRK is designed around supported eBay APIs—not credential sharing, screen scraping, or a fragile browser bot.
- OAuth connection
- Inventory + offer
- Fee preview
- Seller approval
- Production publish
Marketplace writes remain disabled by default.
INTEGRATION PRINCIPLE
Use the direct API where supported.
Export cleanly where it is not.
eBay receives the deepest initial integration because its official APIs cover the full commercial lifecycle. Other channels can receive a Universal Listing Kit until a reliable, authorized publishing path exists.
END-TO-END SCOPE
More than creating
an eBay description.
The integration begins before publication and continues after the sale. Every external action is written back to the Item Record.
SELLER CONNECTION
OAuth authorization, privilege preflight, marketplace eligibility, and secure token lifecycle.
CATEGORY INTELLIGENCE
Category trees, required and recommended item specifics, condition values, and policy-aware validation.
INVENTORY
Inventory locations, SKU-linked inventory items, product details, condition, quantity, and image references.
OFFER
Marketplace, price, format, category, business policies, listing description, and expected-fee preview.
PUBLICATION
Explicit seller approval, idempotency and ambiguity recovery, publish, revise, withdraw, and audit history.
FULFILLMENT
Orders, buyer-selected service, ship-by deadline, labels through supported providers, tracking submission, and status.
FINANCES
Fees, charges, credits, earnings, payouts, refunds, and realized-profit reconciliation.
POST-SALE
Returns, disputes, outgoing evidence, returned-condition comparison, and response package preparation.
PUBLICATION TRANSACTION
No silent marketplace write.
The final publish operation is the last step of an explicit transaction. Required policies, inventory location, package facts, truth checks, fee preview, price, and seller approval must already be present.
- Truth Preflight clear
- Category requirements complete
- Package values confirmed
- Seller approval recorded
FAILURE RECOVERY
Timeout does not mean
“try publish again.”
When a write response is ambiguous, LSTWRK should query eBay for the offer or listing state before another non-idempotent operation. This protects sellers from accidental duplicate listings.
AUTHORIZATION
Invalidate local token state after authorization failures and require a clean reconnect.
RATE LIMIT
Use bounded exponential backoff, preserve the job, and surface the dependency to the seller.
VALIDATION
Translate API errors into the exact missing category aspect, policy, image, package, or seller field.
AMBIGUOUS WRITE
Recover by SKU / offer lookup and reconcile the external ID before attempting another operation.
PARTIAL SUCCESS
Persist each completed external step so a later job resumes rather than repeating the whole transaction.
KILL SWITCH
A deployment-level marketplace-write flag defaults off and can stop all consequential writes immediately.
CURRENT BUILD STATUS
Architecture complete.
Credentials not fabricated.
The website and adapter boundaries are built. A real eBay developer application, Sandbox users, OAuth credentials, seller policies, inventory location, and end-to-end publication test are still required before the integration is described as live.
Open the current preview