How to use a Righthand with Lemon Squeezy
Prepare a reviewed digital-order status exception brief from approved Lemon Squeezy inputs, with a worked example, complete brief, access checks, and reconciliation.
Quick answer
Use a Lemon Squeezy order extract to prepare a status exception brief for the digital-product operator. Preserve store identity and the original order state so a failed or refunded transaction does not become an assumed active purchase.
Start with a digital-order status exception brief that the digital-product operator can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.
Establish the input route
Lemon Squeezy’s order object documents states including pending, failed, paid, refunded, and partial refund, alongside currency and refund-related values. Official Lemon Squeezy reference, checked October 6, 2026.
The operator should supply an approved order extract with its store reference and timestamp. If using a verified connected read, confirm that it targets the intended store and returns the required order fields. Omit personal customer details when an order reference suffices.
Check the current integration directory and Righthand setup documentation. A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.
Worked input and output
These three records are synthetic illustrations, not customer results or a hands-on integration test.
| Approved input | Proposed review output |
|---|---|
| LS61: paid order for variant V1 | Include paid-state evidence for owner review |
| LS62: partial refund; original total remains present | Show original total and supplied refund amount separately |
| LS63: failed order shares email with LS61 | Keep distinct order identity; do not merge into one purchase |
The exception brief is a record-state review, not an entitlement engine. LS62 should preserve its partial-refund state instead of replacing the original total with an unexplained net figure. LS63’s shared contact identifier does not make its failed order equivalent to LS61.
A complete first-run brief
Use an approved Lemon Squeezy order extract and product mapping for October 12–16, 2026. Fields: store reference, order ID, product/variant reference, status, currency, total, refunded amount, created time, updated time. At Monday 9 AM America/Los_Angeles, prepare a digital-order status exception brief as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: digital-product operator. Do not issue refunds, alter licenses, cancel subscriptions, change products, or send customer messages. Result check: Compare state and currency with the original order extract; independently inspect every partial-refund item.
A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.
Reconcile before widening the task
Do not mix formatted currency strings with raw numerical values until their units are clear. An order record also does not establish the current status of every related subscription or license. Request the relevant separate source if the owner asks an entitlement question.
Use one store and one product family for the first support review. Ask the operator to trace LS62’s refund evidence and LS63’s separate identity. Reuse the brief only after the owner confirms which order states belong in their internal exception queue.
For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review Pricing using the actual preparation workload and correction effort.