Seller side: makers and suppliers
The Sell hat
What it is.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
C0825 What does the Sell hat do?
It is a capability mode chosen after sign-in. It records that you intend to post offers and report inaccuracies. It is not an account type and does not create a profile or listing on its own.
C0826 Is the Sell hat a separate account?
No. A hat is a preference on one verified session. ET keeps no user table, so there is no seller account to hold anything.
C0827 Can a seller choose both hats?
Yes. "Both" combines exploring with the planned Sell features, and a person can be a buyer one day and a maker the next.
C0828 What stops the Research hat from posting?
A code-level gate. A session set to Research is refused if it tries to post an offer. This is described in project notes and has not been independently tested.
C0829 What does a seller need before posting could work?
A verified sign-in, the Sell hat, and the production write path to be switched on. The last is the part that is not confirmed.
C0830 Can I post an offer today?
Not in any way we can confirm. Production writes were documented as refused until a process-bound verification ships, and the current state has not been verified.
C0831 What is “process-bound verification” in plain words?
A check that a write really comes from the running, signed-in app on your machine and not from a copied token or script. Until it exists, writes stay refused rather than risk fake posts.
C0832 Can a seller report an inaccuracy about their own entry?
Reporting is meant for the Sell hat and is subject to the same refused-writes state. For now, write to us through data rights.