Search and filter
Browse the resale catalog by search text, category, condition and listing mode, with a sort selection.
Columbus Direct Edge / Functions & workflows
Commerce, from listing
to fulfillment.
Explore the buyer, auction and seller workflows inside Columbus Direct Edge, and the engineering that connects catalog discovery, stock reservations and payment-driven order changes.
Functional scope
Explore 12 capability areas.
01Buyer experienceCatalog & discoveryA resale storefront for discovering products and viewing listing images.
Listing presentation
Inspect individual product pages, listing and gallery images, featured items and related listings.
Catalog data contract
A listing-repository contract separates the storefront from database-backed and snapshot-backed catalog implementations.
02Catalog operationsImages & importsImage inspection and command-driven imports support a changing resale catalog.
Image inspection
Inspect image bytes, MIME type and dimensions. The gallery inspector accepts valid JPEG, PNG and WebP inputs within its configured size limit.
Bounded gallery imports
Import listing galleries from JSON or CSV manifests in bounded batches. A dry run validates the batch without downloading or writing.
Resume and traceability
Import records retain progress and a manifest hash. A resumed run checks that its source manifest has not changed before continuing.
03Buyer experienceBuyer accountsBuyer identity, verified email and account-linked order history support repeat customers.
Registration and access
Register, sign in and verify an email address. Account and bidding routes use authentication and verification guards.
Account history
View account-linked orders, order details and bids. Signed-in purchases retain their buyer association.
Guest and account checkout
Guest purchases and signed-in purchases have distinct checkout paths. CDE is presented as its own commerce product, with its own buyer and order workflows.
04Purchase workflowCart & checkoutCart previews and account or guest checkout connect product selection to a purchase.
Cart lifecycle
Add a listing, inspect the cart and its summary, remove an item or clear the cart before checkout.
Purchase totals
Build an order with item, shipping and tax totals. Checkout and paid-state handling compare the expected purchase amounts.
Checkout sessions and guidance
Create checkout sessions and present readiness, success, cancellation and contextual error messages. An existing open session can be reused in the applicable retry path.
05Purchase workflowAuctions & biddingAuction participation connects verified bidding with buy-now and winning-bid purchase workflows.
Verified participation
Authenticated, email-verified buyers can place bids through a rate-limited route.
Coordinated bid writes
Bid handling uses a database transaction and row lock to coordinate changes to the auction record.
From auction to order
Winning-bid checkout and buy-now behavior connect auction participation to the purchase workflow. The recorded auction fixtures cover both bidding and checkout.
06Transaction integrityInventory reservationsOrder-bound stock reservations keep purchase retries tied to the intended transaction.
Order-bound stock
Checkout reserves listing inventory against an order, retaining the reservation’s owner in the purchase state.
Retry handling
Open-session reuse keeps applicable checkout retries attached to the intended order rather than starting another independent purchase.
Expiration and ownership
Expiration handling checks reservation ownership before releasing stock. Paid-order handling also checks ownership for guest and account purchases.
07Purchase and fulfillmentShipping & taxShipping and tax calculations contribute to purchase totals and seller fulfillment records.
Configured quotes
Shipping estimates and tax quotes use configured rules to contribute to the purchase total.
Order context
Shipping and tax amounts remain part of the order information used by checkout and payment-total checks.
Seller review
Shipping records, tax views and fulfillment context support operational review alongside sales and order records.
08Transaction integrityPayment eventsVerified payment events cross a guarded boundary before order state changes.
Gateway boundary
A checkout gateway connects the order workflow to Stripe checkout-session handling. Payment events enter through a dedicated verification boundary.
Event validation
Incoming events are checked for an HMAC signature, timestamp, expected event structure and configured payment mode before the relevant order handler runs.
Rejection and diagnostics
Malformed and invalid events have rejection paths. Diagnostic forwarding is guarded separately from the buyer purchase flow.
09Transaction integrityOrder finalizationGuarded finalization checks totals and record state before accepting a payment-driven order transition.
Totals and state
Payment-driven finalization checks expected totals and current order state, using locks on the relevant order and listing records.
Repeated and late events
Explicit paths handle repeated delivery, late events and stale checkout state without treating every repeated event as a new purchase.
Listing transition
Accepted purchase finalization updates the purchased listing’s quantity and sale state. Reservation ownership connects these updates to the intended order.
10Seller operationsSeller listingsSeller tools manage the listing lifecycle from creation through publication.
Protected workspace
Seller access gates protect listing management and the surrounding seller workspace.
Listing lifecycle
Create, edit, duplicate and publish listings, with listing status controls and contextual failure messages.
Operational consistency
The seller workspace connects catalog maintenance to order and report views. The dated seller-hub suite checks several workspace behaviors, including access gates.
11Seller operationsOrders & reportsOrder review and fulfillment updates are connected to sales, shipping and tax reporting.
Order review
Search seller orders and filter by status, inspect individual orders and review records needing attention.
Fulfillment updates
Protected seller actions update order status and fulfillment information for the operating workflow.
Sales, shipping and tax
Review sales reports, shipping information and tax views. Recorded report fixtures check reconciliation, protected access and safe failure presentation.
12Storefront supportContact & request protectionContact handling, request guards and security headers support the storefront’s customer-facing boundaries.
Customer contact
A contact form supports customer inquiries with request throttling and contextual status messages.
Request boundaries
Route guards, security headers and request protections support the storefront, account and seller workflows.
Buyer information
Help, condition, shipping, returns, privacy and Terms pages provide supporting purchase information. The dated verification record identifies a Terms attribution copy follow-up.
No matching capabilities.
Try a broader term or clear the filters to explore all areas.
Connected workflows
Follow the work through the system.
Buyer journey
Discover → Choose → Purchase
Search the catalog, inspect condition and images, add an item to the cart, then use guest or account checkout with shipping and tax in the order totals.
Auction journey
Verify → Bid → Checkout
A verified buyer places a bid through a guarded transaction. Winning-bid and buy-now workflows connect the auction result to checkout.
Inventory & payment
Reserve → Verify → Finalize
Stock is reserved against the intended order. Payment-event checks and record locks coordinate finalization, repeats and expiration handling.
Seller journey
Publish → Fulfill → Review
Maintain listings, review orders and update fulfillment. Sales, shipping and tax reporting keep the seller’s operating records connected.
Scope & evidence
Functions, engineering and a dated review.
This directory organizes CDE into 12 capability areas. These are editorial groupings of connected responsibilities, not a function count or test-coverage percentage. The supplied inventory was reconciled with the dated engineering case and focused inspection of the maintained source.
Recorded September 5, 2026: 226 tests · 224 passed · 2 assertion failures · 0 errors · 4,725 assertions. The two follow-ups concern payment-setup guidance and configurable parent attribution in Terms.
The recorded run used an isolated application copy, SQLite in memory, fixture payment gateways and mail, and disabled outbound socket/cURL functions. Results describe that environment and the behaviors exercised. The application tests were not rerun for this directory update.
Explore the engineering
The architecture behind the workflows.
Inspect the application’s architecture, measured source, rebuild assessment and verification record in the Columbus Direct Edge engineering case.