> For the complete documentation index, see [llms.txt](https://faqs.splendidspoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faqs.splendidspoon.com/managing-my-account/can-i-make-changes-to-my-order-after-the-cutoff-time-hypw0vbmf.md).

# Can I make changes to my order after my "edit by" date?

After your "edit by" date, we cannot guarantee that edits can be made to your order - including changing meals, editing a delivery address, or canceling the order. These cutoff times are important for ensuring that our Splendid Spoon team and delivery partners have enough time to prepare orders and get them to you on time! While our customer service team will do their best to accommodate any last-minute requests, once the order has been fulfilled by our warehouses, we can't edit the meals, cancel the order, or offer refunds or credits. As a reminder, you can find the deadline for editing, skipping, or canceling your order on the "Your Plan" tab of your [splendidspoon.com](http://splendidspoon.com/) account. Also, keep an eye out for our reminder emails alerting you of your next order editing deadline! If you have any further questions about this, please reach out directly to us.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faqs.splendidspoon.com/managing-my-account/can-i-make-changes-to-my-order-after-the-cutoff-time-hypw0vbmf.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
