Do not copy a double-price formula into every shop. Mall Together shows a recommended selling price, but no current official source publishes a universal maximum markup. The useful answer is a repeatable test: establish one clean day at the recommended prices, change a small product group, then use store income, visits, stock movement, and the end-of-day report to decide whether the extra margin helped or merely stopped sales.
Current-build boundary: this guide was checked on August 13, 2026. Mall Together released on July 24 and the newest official announcement available during research was v1.11, dated August 11. The developer added daily store statistics in v1.06, more loan choices in v1.09, an eighteenth store in v1.10, and new racks for the Music, Tech, and Bakery shops in v1.11. Older launch footage and community price samples remain useful for identifying the interface, but not for declaring a permanent price ceiling or a current unlock table.
Read cost, price, and stock as three different signals
The tablet separates information that is easy to blur together. In a store, Product is the buying screen: it shows the cost of a case, the cost per unit, the quantity in each case, the amount already inside the shop, and the amount elsewhere in stock. Set Price is where you choose the customer-facing price. Inventory tells you what is physically available. A large number beside a product on the buying screen is therefore not proof that customers will pay that number.
The official Household Appliances screenshot provides a clean example. A case of six Pink Microwave Ovens costs $732.82 and the tablet rounds the displayed unit cost to $122.14. That arithmetic is about procurement:
| Question | Calculation | What it tells you |
|---|---|---|
| What is one item costing the mall? | Case cost ÷ items in the case | The break-even cost before wages and other spending |
| What is the gross margin on one sale? | Chosen selling price − unit cost | How much room the product contributes before overhead |
| What can one full case return? | (Selling price × case quantity) − case cost | The cash contribution if every item in that case sells |
| How much cash is tied up? | Case cost × cases purchased but not sold | The amount unavailable for wages, contracts, racks, and emergency restocks |
Do the case calculation before ordering, especially in an expensive store. A $732.82 appliance case exposes far more cash than a $7.50 box of twenty Milky Biscuits. That does not automatically make the appliance bad or the biscuit good. It means the appliance needs a stronger cash reserve and a clearer sales signal before you queue several cases.
The community-maintained price list is also asymmetric: it has verified acquisition costs for a small appliance and vending sample, but very few current recommended retail prices. Treat a blank recommended-price cell as unknown. Do not turn a shelf label, a Demo number, or a price from another shop simulator into the missing value.
Build one baseline day before testing a markup
Use the recommended-price button for the first controlled day. Community testing consistently reports that this is the low-risk baseline, while also admitting that the exact rejection point above it has not been measured. A baseline day gives you something more useful than a borrowed percentage: the behavior of your own shop with its present contracts, racks, staff, traffic, and stock.
- Fill every tagged selling position that you intend to measure. A product cannot prove demand while its rack is empty. If a line is already short, either refill it or leave it out of the experiment.
- Set the tested products to their displayed recommended values. Do this before opening so the whole trading day uses one state.
- Record the starting shop quantity and warehouse quantity. The inventory display distinguishes items in the store from boxes in stock; v1.05 also made box counts visible even when boxes are on the floor.
- Run a normal day without adding another store or contract. A new shop changes traffic, labor, stock pressure, and available cash at the same time, which ruins the comparison.
- At closing, capture income, visits, sold amounts, out-of-stock warnings, and the price-perception message. v1.06 added store and machine statistics to the tablet and the daily report. Those daily statistics reset after the day ends, so write them down before advancing.
If the baseline already produces empty racks, the next move is not a higher price. First prove whether the gap came from under-ordering, the wrong rack type, an untagged warehouse position, or a stocker bottleneck. Raising a price in that state can hide demand behind a logistics failure.
Change one cohort, not the whole mall
After the baseline, choose a small group that you can observe without confusing it with the rest of the shop. One rack family or two products with similar starting stock is enough. Increase those prices by one modest, reversible step; leave the control products at the recommended value. Run the complete day with the same contract set and without moving the shop.
The test has three possible outcomes:
| What you observe | Likely reading | Next action |
|---|---|---|
| The tested stock falls at a similar rate, store income rises, and the report stays positive on price | The step did not reveal a penalty in this day’s conditions | Keep the tested value for another day, or make one more small step on the same cohort |
| The tested items stop moving while recommended-price controls keep selling | The change probably crossed a useful tolerance point | Return to the last value that still moved; do not average the failed price across every product |
| Both test and control products sell poorly | Price is not isolated as the cause | Check visits, opening state, checkout throughput, stock, rack tags, and product variety before changing price again |
Avoid changing prices halfway through the day if you want usable evidence. The daily total cannot tell you which half produced the result. Also avoid using one quiet day as a universal ceiling: traffic and stock composition can change, and the game has received rapid economy-adjacent updates since launch.
The much-circulated reference price × 2 − $0.01 rule comes from a different game. The supplied Mall Together pricing reference labels that preset unconfirmed. It can be a deliberately risky experiment on one cheap cohort after you have a baseline; it is not a verified Mall Together answer and should never be applied mall-wide on the strength of the formula alone.
Let the daily report diagnose the lost money
Price perception is only one line in the report. Match it with the operational totals before deciding that a markup succeeded.
- Good price message, weak income, low visits: the sale price is not the main bottleneck. Opening another store, improving the active assortment, or dealing with traffic may matter more than another pricing pass.
- Good price message, healthy visits, many stockouts: demand is reaching the shop but the mall is not converting all of it. Increase reorder depth for the lines that actually emptied, not for every item in the catalogue.
- Healthy visits, full racks at close, weak sales on the tested cohort: compare it with the recommended-price controls. If only the marked-up group stalled, reverse the last step.
- Income rises while sold units fall sharply: the higher margin may be hiding lost throughput. Keep the price only if the cash gain is real and the remaining stock is not blocking the next contract or payroll.
- Zero customers is displayed after 22:00: v1.03 explains that any visible straggler is leaving and will not spend. Do not extend the day waiting for one more sale.
Keep a compact notebook with day, product cohort, price state, starting stock, ending stock, store income, visits, and report message. That is enough to identify the last successful step. Exact customer tolerance is still an evidence gap; your log turns it into a bounded local answer instead of an invented global rule.
Make ordering support the experiment
A pricing test fails if the buying queue empties your bank account before customers arrive. Use the tablet’s case quantity and stock columns to build an order around expected gaps, not around the visual size of the product list.
For each product, ask in this order:
- Is its selling rack tagged and compatible? The official Demo Update 2 added rack-type information before contract signing, on the box, on the rack, and before buying a rack. Check that chain before buying the contract’s products.
- Is there already a case in store, warehouse, or on the floor? v1.05’s inventory count includes boxes outside racks. Sort the count from low to high so the real gaps rise to the top.
- Can the shop sell the case before the cash is needed elsewhere? High-cost cases deserve a smaller starting order until a full day proves movement.
- Will the remaining balance cover labor and one ordinary refill? A new contract that leaves no operating float is not affordable merely because the Buy button is active.
The official controls provide a faster but still deliberate order loop. Hover a product and press T to add it to the cart; press Y to purchase everything currently queued. Both bindings can be changed under Options → Controls. Review the cart total before using Y—speed should reduce clicking, not remove the cash check.
Contracts also award XP and unlock products, which makes them tempting as progression purchases. Use a three-part gate before signing: the level requirement is met, the fee is available without consuming the operating reserve, and the necessary rack type can be placed. If any one is missing, the contract increases pressure without increasing reliable sales.
Fixed-price machines need a different profit test
Drink, snack, and cigarette vending machines do not use the store Set Price workflow. The official machine interface shows Equipment, Contracts, Market, Workers, and Inventory, but no Set Price tab; the supplied community FAQ likewise records vending and the massage chair as fixed-price services. Repeatedly searching the store pricing screen will not reveal a hidden slider.
For a machine, the adjustable decisions are placement, product availability, contract depth, and restocking. Judge it by machine income, units sold, and visits in daily statistics. If traffic is weak, moving or diversifying the machine is a more relevant experiment than trying to force a price change that the interface does not offer.
The cost-risk rule still applies. The official snack-machine screenshot shows twenty units per box across the visible selection, with case costs ranging from $7.50 to $69.75. A low unit cost does not help if the machine never receives visits; a higher-cost refill may be justified only after the machine’s sold count proves demand.
Use online orders only while the queue stays serviceable
Online orders create another demand channel, but they can turn a clean pricing day into a fulfillment test. Since v1.05, the host has two controls in the Online Orders section: one stops new orders, and the other enables a larger flow. The extra-orders option is off by default.
The same official update sets a concrete queue rule. Six orders can be active simultaneously. If they are left unfinished, another will not arrive; when the active count stays below six, the day can provide as many as nine orders. Co-op capacity also affects the daily amount, and only the host sees these settings.
Turn extra orders off for the baseline if you cannot reliably separate shelf sales from packed orders. Turn them on when stock, checkout, and co-op roles are stable enough to keep the queue below the six-active cap. From v1.09 onward, the notification names the relevant store, so a co-op team can assign fulfillment without opening each tablet page just to discover the source.
Do not empty a shop’s last shelf units into an order without checking the floor. The order may pay, but the visible stockout can suppress ordinary sales and contaminate the day’s markup test. Reserve a clear fulfillment box or restock the rack immediately after packing.
Spend on the bottleneck that the day exposed
At closing, choose among contract, stock, worker, training, expansion, or cash reserve. The best choice is the one that repairs the measured loss:
| Observed limit | Investment to consider | Delay this instead |
|---|---|---|
| Lines form while stocked products wait | Cashier coverage or faster checkout training | A second contract that adds more demand to the same till |
| Tagged racks empty with boxes available | Stocker coverage, faster filling/walking training, or a rack-layout repair | A markup test that would disguise lost fulfillment |
| Warehouse gaps repeatedly cause floor stockouts | A deeper order for proven fast movers | Decorations or an untested high-cost catalogue |
| Visits and sales are stable but the assortment is exhausted | The next affordable contract plus its racks and opening stock | A broad reorder of slow lines |
| The store is profitable but consumes all working cash | Reserve accumulation | A new shop whose setup fee leaves no refill budget |
v1.07 added cashier training for faster checkout and stocker training for faster filling and walking. If you need to retag or reorganize without an employee moving the same boxes, v1.02 added a pause control for store and vending stockers. Pause only for the repair window, then restart the worker from the same section.
Old launch recordings require special care here. The supplied 6-hour-40-minute local playthrough was captured from a launch build dated July 24. It eventually shows workers failing to place goods and the player reporting a broken save. That is valid evidence about the recording, not about v1.11. The very next official patch changed Stocker Workflow 1 so a stocker no longer stands indefinitely with a box when the tagged warehouse location is unavailable, and it made stockers choose the lowest-quantity box first. Update the client and inspect tags, free warehouse positions, workflow selection, and paused state before treating an old video symptom as a current permanent bug.
Use store shutdown as a recovery tool, not a panic button
If a shop was placed badly or opened too early, v1.04 added Store Shutdown. Only the host can use it in online co-op, and it is performed at 9:00 while the mall is closed. The rules make shutdown a controlled relocation option:
- cash registers, store racks, and warehouse racks are boxed and left outside the shop;
- the initial store setup payment is refunded;
- the cashier and stocker are dismissed, with their first-time hiring payments refunded;
- signed contracts become available again when the same shop is reopened;
- purchased design elements remain owned;
- store and warehouse expansion payments are refunded.
Shutdown is useful when the shop type is sound but the location or timing was wrong. It does not erase the cash already tied up in unsold cases, so account for the boxed inventory before opening another expensive shop. If the underlying problem is only a failed markup test, reverting prices is cheaper than rebuilding the store.
v1.09 added three more bank-loan choices. Treat a loan as a bridge for a measured bottleneck, not as proof that an unaffordable store is ready. Before borrowing, name the repayment source: an already-tested product cohort, a checkout fix, a known stock gap, or a contract whose required racks and first cases are budgeted. If the plan depends on an unverified markup ceiling, the debt is amplifying an assumption.
Keep the guide aligned with the live build
Mall Together is changing too quickly for a frozen universal price table. As of this check, the live official count was eighteen stores: the Gift Shop arrived in v1.08 and the Sunglasses Store in v1.10. v1.11 added new S1/S2 racks for Music, an S2 and S3 rack for Tech, and an S2 rack for Bakery. Hardware was announced for a later update, so it is not included here as a currently available store.
Recheck three places after a patch: the current recommended value in Set Price, the case quantity and unit cost in Product or Market, and the rack type required by a contract. Preserve your old daily log, but label the last tested build. When one of those inputs changes, establish a new recommended-price baseline before resuming the markup ladder.
The practical endpoint is not one magic percentage. It is a shop where every chosen price has a recorded baseline, the stock system can satisfy the resulting demand, and the next contract does not consume the cash needed to operate the mall you already built.
Official game and update sources
Game identity, features, screenshots, and store list: Mall Together on Steam. Version-specific controls, statistics, workers, online orders, shutdown rules, loans, and store additions: official Mall Together announcements. Pricing-ceiling cautions and launch samples were cross-checked against readable community references and a locally supplied launch-build playthrough; they are intentionally described as bounded evidence rather than official constants.