Quick answer

After Version 1.0, stop using the old Reputation-and-purchase-contract model as the first explanation for a shop result. The official 1.0 notes say Reputation was reworked into Shop Recognition, customer purchase feedback no longer changes Reputation in the old way, and the bonuses from removed purchase-contract upgrades moved into Shop Recognition.

If a high-value item is not selling, first check the current Shop Recognition state, the shop and customer path in the current build, and whether the expectation came from an Early Access guide. Launch-week community posts mention symptoms such as Saturn or Diamonds not selling, but those reports do not prove a universal item bug or make Shop Recognition the sole cause.

What changed in Version 1.0

The 1.0 update changed the vocabulary and ownership of the shop progression loop:

  • the old Reputation system was reworked into Shop Recognition;
  • customer feedback when making a purchase no longer changes Reputation in the old way;
  • players obtain Shop Recognitions that increase shop reputation and profits; and
  • shop sales upgrades were reworked while purchase-contract upgrades were removed, with those bonuses integrated into Shop Recognition.

That is a system change, not a promise that every sale problem has one explanation. Read the current menu labels and upgrade path before copying an older checklist.

Use Shop Recognition as the current model

When a shop result looks different after 1.0, keep the diagnosis tied to the action you were taking:

  1. Open the current Shop Recognition information and identify which recognition or shop progression step the build exposes.
  2. Separate a progression question from a customer-reach question. Version 1.0 also changes shop management and customer access, so a sales symptom should not be assigned to an upgrade system without checking the shop flow.
  3. Compare the item, the shop state and the customer path in the same session. Keep the item and the observation together instead of treating one old price expectation as a permanent rule.
  4. If the result is repeatable, record the exact item, shop state and build before looking for a narrower item page.

This gives the current system a clear first check while keeping the evidence boundary visible.

If an item stops selling

Use this bounded diagnostic order:

  1. Check the current progression label. Confirm that the screen is using Shop Recognition and not an old Reputation or purchase-contract instruction.
  2. Check customer access. Look at the shop path and the customer route in the current layout, especially if the symptom appeared after a shop-management change.
  3. Check the observation. Note the item, the displayed reaction and whether the same result occurs again under the same shop conditions.
  4. Check the build boundary. Read the current official announcements before treating an Early Access explanation or an already-fixed launch issue as a current universal rule.

These checks help distinguish a changed progression model, a shop-flow problem and a reproducible item-specific report. They do not turn a community symptom into a confirmed global bug.

What the current evidence does and does not establish

The official 1.0 record supports the Shop Recognition rework and the movement of sales bonuses into that system. Community discussion is useful for the words players use when a valuable item does not sell and for deciding what to reproduce.

The available sources do not provide a universal Saturn or Diamond failure rule, a complete current price table or a single-cause explanation for every sales result. Keep those claims separate from the official system change until a current reproducible source supports them.

Sources

Last verified: September 10, 2026. Recheck Shop Recognition labels, customer flow and sales behavior after future updates.