Teams usually find gaps in marketplace when an exception exposes an unclear decision. A better starting point is to define seller eligibility, listing ownership, buyer state, payment, fulfillment, dispute, and removal. This matters because unclear platform responsibility leaves money and access between systems when a transaction fails.
Turn "done" into observable behavior: Marketplace
Acceptance criteria for marketplace should identify the actor, starting state, action, durable result, denied path, repeated action, and recovery evidence. The interface may report success while unclear platform responsibility leaves money and access between systems when a transaction fails. The criterion therefore has to compare visible feedback with the server-calculated commercial record and provider-confirmed state.
Cover the states that change the decision: Marketplace
Test ready, empty, invalid, denied, delayed, duplicate, partial, successful, and recovered states where they apply. Add a case in which the browser closes, a provider callback is delayed, or the customer repeats the action. Each case should say whether input is preserved, whether retry is safe, and which record a reviewer inspects. Avoid criteria such as "works" or "implemented" because two reviewers can interpret them differently.
Test authority, not visibility: Marketplace
The expected behavior must hold for an allowed actor, a denied actor, a revoked role, and a direct request that bypasses the normal interface. A denial should leave protected state unchanged and produce a useful audit record without exposing secrets. For marketplace, the accountable actor is the customer completing a commercial transaction.
Attach evidence to every important claim: Marketplace
Use amount calculations, signed callbacks, idempotency records, fulfillment state, and reconciliation output. Record the environment, configuration, and time range so another reviewer can reproduce the result. A passing test supports only the behavior it exercised; it does not prove every security, accessibility, performance, or operational claim. Monitor reconciliation gaps as a release signal.
Decision map: Marketplace
- Seller eligibility. Name the owner, authoritative record, expected state, and denial behavior for this part of marketplace.
- Listing ownership. Document the normal transition, one interrupted transition, and the smallest safe recovery.
- Buyer state. Attach a reproducible test, dated result, and reviewer who accepts the remaining risk.
- Payment. State the input, output, permission boundary, and removal condition before adding automation.
- Fulfillment. Record how repeated action behaves and which evidence distinguishes retry from duplication.
Boundary cases: Marketplace
- When the recorded value for seller eligibility changes after listing ownership is stored, name which value wins and how the losing state is reconciled.
- If evidence for buyer state becomes unavailable while the marketplace request is in progress, preserve enough context to distinguish rejection from partial completion.
- A repeated action involving payment should return the existing result or expose the possible duplicate effect before retry.
- A denied change to fulfillment must leave authoritative state untouched and create an audit record that reveals no secret.
- Recovery should restore the smallest trustworthy state first, then verify the visible marketplace outcome against the maintained record.
Measure the decision, not activity: Marketplace
Track reconciliation gaps and successful completion. Before collecting results for marketplace, define each measure's population, environment, time window, and owner. Activity is useful only when it clarifies whether the protected marketplace outcome became safer or easier to recover.
Set the investigation threshold for marketplace in advance. The acceptance review should also name the permitted response, the evidence required to close the issue, and the next review date. Stop collecting marketplace data when it no longer distinguishes success, denial, delay, duplication, or recovery, or when it no longer changes a decision.
Sources and local proof: Marketplace
These primary references document platform behavior relevant to marketplace. For marketplace, those references establish terminology and constraints; they do not verify the local implementation.
- Authorization Cheat Sheet
- Logging Cheat Sheet
- How Checkout Works
- Fulfill Orders
- Handle Payment Events with Webhooks
Any publishable marketplace claim still needs dated local evidence: configuration, test output, screenshots, logs, queries, or recovery results from the named product. The acceptance review should say exactly which artifact supports each important claim.
A related InMyDraft example: Marketplace
InMyCompany provides a local example of an inspectable product boundary relevant to marketplace. Its project catalog records this implementation detail: Tax estimates are computed from the company's own configurable rates, clearly labelled as planning estimates rather than official filings, and surfaced on the dashboard and in reports.
The comparison between InMyCompany and marketplace is deliberately narrow. It shows how one product makes state and evidence visible; it does not prove that every marketplace recommendation has been implemented. Use the InMyCompany example to review marketplace, not as a substitute for testing the product in scope.
Review checklist: Marketplace
- Given a valid starting state, the customer completing a commercial transaction can complete the intended marketplace outcome.
- Invalid and unauthorized requests leave the server-calculated commercial record and provider-confirmed state unchanged.
- A repeated action does not duplicate a protected side effect.
- The team can demonstrate that it can trace one transaction through cancellation, repeated events, refund, and operator reconciliation.
- Failure and recovery produce evidence another reviewer can reproduce.
A marketplace decision is ready for the next stage when another accountable person can reproduce the evidence, explain the failure boundary, and perform the recovery without relying on the original author's memory.
