Store API Order Filtering Limitations - Design Intent Question

[leosin]

Hi Medusa team! 👋

First, I want to express my appreciation for the excellent work you've done with Medusa. The framework's flexibility, modern architecture, and developer experience are truly impressive. It's clear that a lot of thought has gone into building a robust foundation for e-commerce development.

However, as a developer working with Medusa, I sometimes find it challenging to understand the intended design philosophy, particularly regarding the Store API. I'd love to get some clarity on whether certain limitations are by design or if they're areas planned for future enhancement.

Specific Example: Order Filtering in Store API

Currently, the /store/orders endpoint only supports filtering by basic order status:

status: "pending" | "completed" | "draft" | "archived" | "canceled" | "requires_action"

However, in real-world e-commerce scenarios, customers typically need to filter orders by:

• Payment status (paid, pending payment, refunded, etc.)
• Fulfillment status (shipped, delivered, processing, etc.)
• Combined states that make sense to end users

For example, customers commonly want to see "orders that have been shipped" or "orders awaiting payment" - these are fundamental user experiences in any e-commerce platform.

The Core Question

This brings me to my main question: Is this limitation intentional?

Option A: Are these features planned for future releases of the Store API?

Option B: Is the Store API intended to provide only basic functionality, with the expectation that developers will create custom endpoints for more specific business logic?

Why This Matters

Understanding the design intent would help developers like myself make better architectural decisions:

• If it's Option A, we might wait for official updates or contribute to the roadmap
• If it's Option B, we'd focus on building custom API layers from the start

Both approaches are valid, but knowing the intended direction would save development time and align better with Medusa's vision.

Request for Clarity

Could the team provide some guidance on:

1. The intended scope of Store API - Is it meant to be production-ready for most use cases, or a foundation for custom development?

2. Roadmap for Store API enhancements - Are there plans to add more filtering capabilities?

3. Best practices recommendation - Should developers typically extend Store API or build custom endpoints for business-specific needs?

Thanks for taking the time to clarify this! Understanding the framework's philosophy will help the community build better applications and contribute more effectively.

Looking forward to your insights! 🚀