Returns

Returns is an official Connect v1 capability with two operations.

There is no separate return-status API in Connect v1.

Ownership

• The origin platform owns the consumer return and customer relationship.
• SKUU validates the request, finds the seller order and performs operator
  review before release.
• The fulfilling seller creates the approved return in its own platform.

Receive a return request

When a consumer return is registered, the origin platform sends one signed
return.created event. The event identifies the original order and lines,
requested quantities and optional line reasons. A customer note is optional.

This is a signed webhook delivered to SKUU, not a GET /returns request.

SKUU stores the request for review. It does not route a return merely because
the event was received.

Returns write

After approval, SKUU sends one POST /returns request for one seller order. A
return spanning multiple sellers or fulfilment locations is resolved and split
internally before these requests are sent.

The seller creates the native return and responds with its stable return_id.
The request identity makes an exact retry a safe no-op.

Approval, routing and split decisions are not public request fields. The
fulfilling seller owns its agreed return destination and native return process.
The origin platform communicates the agreed return instructions to the
consumer.

Connect v1 boundary

Inspection, acceptance, rejection after receipt, refund execution, return
labels and customer notifications remain owned by the participating commerce
platforms. They are not additional Connect v1 endpoints or events.

Testing the flow

Joint TESTING proves one signed return request, operator approval, safe routing,
one seller-side return and one exact replay without a duplicate return.

Technical reference

• Deliver a signed Connect event
  defines the exact return.created event.
• Create a seller return
  defines the exact POST /returns request and response.