Yes. Help has a category for it — Feedback & ideas, for telling us what to build or fix.
The app is honest about what happens next: ideas go straight to the team building Metzee, and while we may not reply to each one, we do read them.
Why there is no promise of a reply
Because a promise we broke would be worse than no promise. A suggestion worth building usually arrives several times from several people, and the useful response to it is the thing being built rather than a message saying we received it.
So: read, yes. Answered individually, often not.
What makes a suggestion useful
The problem, not the solution. "I keep losing track of which orders I have packed" is more useful than "add a checkbox", because the checkbox may not be the right answer and the problem always is.
When it happened. Mid-show, at checkout, the morning after. The same problem in two places is two different problems.
How often. Once is a story; every week is a priority.
What you do instead today. A workaround tells us what the feature has to beat.
What belongs somewhere else
Something broken is Technical problem / bug, not feedback. Different queue, faster.
A problem with an order is its own category, and putting it in feedback delays it.
Something about a seller goes to Safety / report someone if it is serious. How to raise an issue
What tends not to get built
A setting for a thing one person wants. Every setting is a permanent cost on everybody who does not use it.
Something that only works if everyone behaves well. The feature has to work on a bad day too.
A copy of another app. "X does this" is a starting point, not a reason.
None of that means do not send it. It means the reasoning you include is doing more work than the request itself.
The suggestions that have landed
The ones that named a specific moment where the app wasted somebody's time. That is the shape worth writing.
More: how to raise an issue, what Metzee will not do, how we make money.