Odyssey order fulfillment checklist for service and product vendors

Start with the official order, not a new payment request

This guide is for a vendor who already has an Odyssey marketplace order. If you still need to register or list an offering, start with the Odyssey vendor guide. Texas providers can also use the TEFA vendor application guide. A provider account, an offering and a customer's order are different records.

Odyssey's official fulfillment instructions describe opening the order in the vendor account, confirming or cancelling it, and saving the relevant fulfillment reference. Services use a receipt or confirmation reference; shipped products use tracking information. Follow the current portal prompts for the order you are handling. Official fulfillment instructions.

Download a fulfillment register

Use the blank order fulfillment register CSV as a private working index. It records the order reference, offering type, confirmation, fulfillment evidence, portal update and payment-matching reference. The download is free and requires no account.

This is not an Odyssey bulk-upload file. Do not upload it to the portal as if its columns were an official schema. Its purpose is to keep your own evidence organized while you complete the required actions in Odyssey.

Separate the four checkpoints

Checkpoint	What to verify	What to preserve
Order accepted	You can fulfill the actual offering, quantity and terms	Order reference and the recorded acceptance
Service delivered or product shipped	The evidence describes what actually happened	Service confirmation or shipment reference
Fulfillment saved in the portal	The reference is attached to the correct order	A portal confirmation or checked date
Payment matched	The payment record corresponds to a bank receipt	Payout reference and allocated amount

An order confirmation is not itself evidence that the service has been delivered. A shipment reference is not interchangeable with a service receipt. A saved fulfillment record is not a bank deposit. The register gives each checkpoint its own place so one status cannot silently stand in for the rest.

Service orders: connect the receipt to the delivered work

Use a stable reference that you can trace back to the service. Odyssey's instructions explain what to use when your system does not generate a confirmation number, including a fulfillment date and time. Check the official guidance before entering a substitute reference. Receipt-reference guidance.

For your private records, make the reference understandable a month later. Record the order it belongs to, the service date and where the supporting service record is stored. Do not use a vague reference such as “done” across multiple orders and expect to distinguish them during reconciliation.

If a service was rescheduled or partly delivered, establish the correct treatment with the official program or support channel before marking the whole order fulfilled. This checklist does not authorize partial fulfillment or create an exception to an offering's terms.

Product orders: verify the shipment reference

Before saving tracking information, check that it belongs to the correct order and that the quantity shipped matches your record. A copied tracking number from the previous customer's order can look plausible while linking to the wrong transaction.

Keep your dispatch evidence and the order reference together. If a shipment is cancelled, returned or replaced, preserve what changed and use the official workflow to resolve the order. Editing a local spreadsheet does not amend the marketplace transaction.

For multiple orders, follow Odyssey's own bulk fulfillment instructions, including its current upload requirements. Review row-level results rather than assuming every row succeeded because the file was accepted.

When does the payment process begin?

Odyssey's marketplace payment article states that a valid tracking or receipt reference starts its Net 30 process and describes ACH payment through Stripe. It also directs vendors to manage transaction documents in its portal and prohibits sharing those documents between suppliers and consumers. Follow those instructions and the terms applicable to your order; do not treat a generic date calculation as a guaranteed bank-arrival date. Official vendor payment guidance.

For this workflow, do not use a GetESAPaid public invoice link as a substitute for the Odyssey transaction. Keep any supporting records private and submit or communicate only through the authorized channel.

Fictional example: an accepted service with missing fulfillment

A provider accepts DEMO-ORDER-104 for a reading session. The service is delivered, but the provider's working sheet only says “accepted.” At the weekly review, there is no saved fulfillment reference or portal check recorded.

The provider checks the order in Odyssey before taking action. If the required reference is missing, they complete the appropriate portal step using the actual service evidence, then record the confirmation and checked date locally. If the reference is already present, they preserve it and investigate the payment stage rather than submitting the same service again.

This example identifies a missing checkpoint; it does not claim that every delayed payment has this cause. Banking setup, review questions or another account-specific issue may require official support.

A focused support request

Use the official support channel and ask one answerable question:

For order [reference], the current status is [exact wording]. The service or shipment was completed on [date], and the fulfillment reference was saved on [date]. Please confirm whether further vendor action is required before the payment process can proceed. The relevant evidence is available in the portal.

Keep the response with the order record. Once money arrives, use the invoice tracking template or your existing accounting process to link the payment to the correct records without duplicating a combined deposit.

Source scope

Official fulfillment and payment instructions were checked September 6, 2026. This page explains those checkpoints and supplies an original working register. It does not certify every state program's offering, refund, tax or settlement rules. GetESAPaid is independent of Odyssey and does not operate its marketplace.

Service bundles: one order can cover several sessions

Odyssey's Vendor Experience article explicitly discusses bundles and says the confirmation reference for a bundle is uploaded after the first session is completed. Read that bundle-specific instruction alongside the current terms for the actual offering; do not infer that every session in the package has already happened. Official service-bundle guidance.

Keep an order-level record and a session-level record. The order identifies the purchased bundle and its official transaction status. The session log records which lessons were actually delivered. This distinction prevents a payment-stage milestone from being mistaken for a complete attendance history.

Fictional four-session bundle

An example order includes four reading sessions. After the first session, the provider follows the applicable portal instruction for the bundle's confirmation reference. In the private service log, only session one is marked delivered. Sessions two through four remain scheduled or outstanding until they actually occur.

If session three is rescheduled, update the schedule and preserve the actual eventual service date. Do not mark it completed just to make the four-session count match the order. If the remaining service cannot be provided, use official support to establish the order amendment, cancellation or refund route before changing financial records.

Exception	Preserve	Confirm through the official workflow
Session rescheduled	Original schedule and actual service date	Whether any order action is required
Part of the bundle cannot be delivered	Delivered-session evidence and outstanding portion	Correct treatment of the remaining obligation
Wrong fulfillment reference entered	Original entry and the correct evidence	How the order reference should be corrected
Refund or cancellation requested	The request, order reference and response	Who can authorize the action and what record changes

This table identifies the questions to resolve. It does not grant permission to partially fulfill, refund or cancel an order outside the program's terms. A local correction or spreadsheet change cannot perform those actions in Odyssey.