Answers for the work behind every order.

Meridian is for DTC founders and the small teams behind growing consumer brands. It is designed for teams that want a more thoughtful way to understand customer requests without losing the context or judgment that makes their brand distinct.

The first workflow is designed to help a team understand a return request, gather useful context about the customer’s situation, ground its guidance in the brand’s own returns policy, and prepare a clearer handoff to a person when a decision is needed.

The intended early-stage outcome is a clearer, more consistent return conversation: the request has useful details, the policy source is kept in view, and the human teammate receives a sensible next step. Meridian is being shaped as an assistant for that work, not as a replacement for your team’s judgment.

Not yet. The early build is not connected to a live policy system or order system. It should not be presented as looking up current orders or retrieving a live version of a brand’s policy.

No. Meridian does not currently guarantee eligibility answers. Its intended role is to surface the request and relevant context, keep the policy source visible when available, and make a human decision easier.

No. Automatic resolution is not yet available. The initial experience is designed to prepare a clearer human handoff rather than approve, deny, refund, exchange, or otherwise resolve a return on its own.

Not at this stage. General operations coverage is not yet available; Meridian’s initial focus is the specific workflow around understanding and handing off customer return requests.

Use the early-access request form to tell Meridian about your brand and the return requests that create the most drag. Early access is not production availability, and the returns assistant is still in an early build.