Store layout for throughput

Scope and current-layout evidence

This guide covers functional retail and service layouts in Big Ambitions 1.0/build 3674. It separates mechanics confirmed by the live interface or developers from aesthetic choices and old Early Access assumptions.

The strongest current evidence is the 1.0 change that product and furniture information now exposes customer capacity and placement requirements. Use those live labels and F1 help as the specification for a build. A screenshot from an older layout can suggest an arrangement, but it cannot override a changed capacity or requirement.

Developer explanations describe the building’s customer-per-hour figure as an upper bound and the capacities of required furniture or product categories as additional bounds. A store therefore performs at the smallest relevant limit, not at the number printed on the lease alone.

Another developer explanation distinguishes simulation while the player is away or using time advance from physical customer movement while the player is inside. When present, blocked aisles, awkward queues, and inaccessible interaction points can matter directly. A robust layout must work in both states.

Build 3674 did not announce a general rebalance of furniture capacity. It fixed several operational defects, including MarketInsider neighborhood selection and employee-quit interruptions. Record the build anyway, because a day with failed staffing or delivery automation is not a clean layout test.

This article deliberately avoids universal blueprints. Shell geometry, entrances, delivery spots, required fixtures, business category, product mix, and patch behavior differ. The method is to calculate a target, place the full customer journey, and validate it on site and off site.

Model the layout as a chain of bottlenecks

A usable design begins with a capacity equation rather than a floor plan. Every required step must support the intended customer rate.

Define target customers per hour T. For a simple retail store, an operational upper bound is min(building limit, capacity supplied for every required product category, checkout capacity, basket or support capacity where applicable, and staffed capacity). Add service, seating, production, or entertainment limits for businesses that require them.

The word every matters. In the developer’s illustrative clothing example, a premises limit of 30 combined with a clothing rack capacity of 10 requires three units of each required rack type to avoid a 10-customer bottleneck. Recheck the current item labels before applying that old number literally.

Calculate fixtures for category i as n_i = ceiling(T divided by live capacity per fixture_i). If one fixture can hold several product variants, confirm whether the displayed customer capacity is shared or category-specific. The catalog’s 1.0 placement hints are the authoritative clue.

Placed capacity is not always staffed throughput. Registers, service desks, counters, and production equipment need assigned employees during each tested hour. Record placed units and staffed units separately. Buying ten checkouts does not create ten lanes when only two cashiers are scheduled.

Do not automatically target the lease maximum. Use a smaller T when observed demand, traffic, promotion, price acceptance, or payroll cannot justify the ceiling. Design modularly so another fixture or lane can be added after repeated saturation.

Survey the empty shell before buying furniture

The best time to prevent a pathing or delivery problem is before expensive fixtures are placed. Map fixed geometry first.

Walk the entire premises and mark customer entrances, employee access, doors, columns, windows, walls, bathrooms, and the delivery spot. Note which doors swing into circulation space and where customers naturally turn after entering. A screenshot or simple grid sketch is enough if it preserves dimensions.

Identify the delivery route from the exterior drop to store storage and each sales fixture. Keep this corridor broad and direct enough for hand trucks and employees. A decorative maze that looks attractive can turn every manual restock into wasted time and can obstruct on-site customers.

Reserve a front-of-house customer loop and a back-of-house replenishment route. They can share space in a small shop, but avoid forcing restocking through the active checkout queue. Put high-frequency restock fixtures closer to storage when the shell permits it.

Check camera sight lines, detector placement, guard requirements, cleaner access, trash or bathroom support, and employee workstations before filling empty corners. Support equipment added last often blocks the route the original plan depended on.

Measure the shell’s actual usable area, not the marketing label alone. Two premises with the same capacity code can feel different because of doors and internal geometry. A blueprint must match both building type and shell code before installation.

Build the complete requirement list

A store is not operational because its main displays are present. Use F1 and the business status screen to create a bill of requirements before opening.

List required sales fixtures by category, checkout or service furniture, baskets where required, storage, cleaning equipment, bathroom fixtures, employee workstations, and security devices. For food or entertainment, expand the list to every production, seating, ticketing, and support stage.

Beside every item, record three separate facts: whether it is mandatory, its customer capacity contribution, and its inventory capacity if it holds stock. These numbers answer different questions. A fixture can satisfy customer throughput while still holding too little stock for the delivery interval.

Record placement rules exactly as shown in 1.0. Some objects need wall access, a valid chair, clearance, power-like adjacency, or a specific room context. Do not discover these rules after hiring employees; place and verify each station while the store is empty.

Add employee-demand furniture only after identifying the actual hires, but reserve space for likely demands. A compact layout with no spare wall or desk position becomes expensive to rebuild when a critical worker requests an object that must be placed at work.

Treat optional product categories cautiously. An added category can introduce another inventory stream and, depending on the business requirements shown by the current UI, another capacity constraint. Verify the impact before rolling a decorative shelf into a fully tuned store.

Place the customer journey in order

Customers should be able to enter, obtain what they need, pay or receive service, and leave without crossing avoidable queues.

Start at the entrance and trace the interaction sequence for the business. In retail this often means basket access, product fixtures, checkout, and exit. In a restaurant it may include ordering, production handoff, seating, waste, and exit. In an office it is entrance to a valid staffed service workstation.

Put the first required interaction where customers can reach it without colliding with the exit stream. Leave clearance on the interaction side of each fixture, not merely around its decorative footprint. Rotate and test objects because a visually adjacent chair or register can still be invalid.

Create queue pockets rather than allowing lines to occupy the main aisle or entrance. During an on-site peak, watch where NPCs stop and turn. Move fixtures based on observed collision points, then repeat the same time block to confirm the improvement.

Aisle width has no useful universal tile count across all objects and camera angles. The practical rule is reproducible passage: the player with a hand truck, employees, and customer groups must pass without forced detours or frozen clusters. Record the narrowest trouble spots.

Keep the exit obvious and unobstructed. Decorative barriers, planters, signs, and tightly packed displays can reduce physical efficiency without changing a capacity number. Beauty should be layered onto a validated circulation plan, not used to define it.

Design checkout and service throughput

The transaction end of the layout often sets the real ceiling because both valid furniture and scheduled employees are required.

For each target hour, record the number of staffed lanes or service positions and the customer graph. If queues appear while demand is below the premises limit, inspect station capacity, assignment, access, and shift handoffs before adding more merchandise fixtures.

Place parallel registers so each employee and customer has an independent approach. Avoid making one queue cross another station’s chair or forcing all customers through a single narrow opening. A second lane that cannot be reached is decorative capacity.

Use the smallest number of staffed stations that clears repeated peaks with a reasonable buffer. Extra furniture can be installed for future growth, but extra payroll should follow measured queues or saturation. Keep placed capacity and active capacity in the ledger.

Schedule handoffs around peaks. If the morning cashier leaves exactly when the afternoon cashier begins, verify no uncovered interval and no invalid reassignment. The hourly graph can conceal short gaps that cause a queue spike and customer dissatisfaction.

Scenario: a 30-cap shop owns three registers but routinely staffs one. The graph plateaus below 30 and on-site customers queue. Adding product racks will not help. Test a second staffed lane during only the plateau hours, compare contribution, and retain it if avoided lost demand exceeds wages.

Balance product fixtures and inventory capacity

Customer capacity and stockholding capacity must be solved together. A layout can pass the customer indicator yet empty before the next delivery.

For each SKU or required category, record fixture customer capacity, fixture unit capacity, number of fixtures, combined display stock, average daily units sold, and delivery cadence. The first pair controls potential throughput; the second pair controls endurance.

Set a store target at least high enough to fill all assigned displays and cover expected sales until the next successful replenishment plus safety stock. If multiple displays carry the same SKU, use their combined capacity. A target below that sum can produce persistent low-inventory warnings.

The 1.0 release changed inventory distribution so a box of an item such as paper bags can be spread more evenly among multiple appropriate fixtures. This reduces a former allocation annoyance, but it does not excuse too-small targets or missing store storage.

Place fast-moving displays nearer the back-room route without sacrificing customer flow. Slow, bulky products may need more reserve space because box size consumes shelf slots. Use the importer or product UI’s current units-per-box information when planning storage.

Scenario: two valid product fixtures each hold enough customer capacity, but the store target covers only one display. One empties late and realized traffic drops. Raise the target, confirm warehouse supply and destination space, then repeat the same weekday before redesigning the floor.

Keep storage and delivery operational

A beautiful sales floor fails when deliveries cannot land or reserve stock cannot be held. Back-of-house design is part of customer capacity.

Use Storage Shelves in stores and reserve pallet-style warehouse equipment for warehouse operations according to current developer guidance. Confirm the live furniture description, because 1.0 also allows Storage Shelves in warehouses and factories, expanding options without changing the need for valid destination space.

Keep the path from delivery spot to storage clear and avoid placing customer queues across it. Test a delivery or manual restock with the same hand truck used in normal work. Count turns and blocked doors; unnecessary travel multiplies across every box.

Size reserve space by boxes, not merely units. Required boxes = ceiling of reserve units divided by current units per box. Product box sizes are visible in current importer interfaces. Add a buffer for support goods and a temporary surge after a large delivery.

Do not overfill the destination. If logistics reports source stock but the store remains short, inspect store shelf space, combined display capacity, target units, route timing, and assignment. A cramped back room can be the real cap even when the sales floor has room.

Separate reserve stock from employee-demand objects and cleaning gear so added furniture does not invalidate access. Mark one flexible bay for a new SKU or packaging change. Revalidate after importing a product with a different box size.

Account for player-present versus simulated operation

Layout validation requires two modes because the game may use abstract calculations when the player is away and physical movement when the player is inside.

Run an off-site test using normal play or time advance and record customers per hour, capacity warnings, and financial results. This establishes whether the abstract configuration recognizes all required objects and staffing.

Then visit during a proven peak without changing settings. Watch entrances, browse paths, queues, service interactions, employee movement, and exits. Record where NPCs wait or reroute. A strong off-site result with poor on-site flow points to geometry rather than market demand.

Do not use a single crowded visit as a precise throughput benchmark. Player presence, arrival timing, and short observation windows create noise. Reproduce the same trouble at comparable hours and save screenshots or notes of the exact obstruction.

After moving furniture, repeat both tests. A change that opens an aisle but accidentally invalidates a camera, chair, register, or required placement can improve visible flow while reducing simulated capacity. Confirm the business status screen remains clear.

For stores the player visits frequently, prioritize robust physical circulation even if an off-site formula would tolerate tighter packing. Time spent navigating around decorations and blocked replenishment routes is a real management cost to the player.

Security and cleaning geometry

Security equipment and cleaning routes should be designed with the store, not appended after all useful wall and floor space is gone.

Map entrances and valuable product zones before placing cameras and detectors. During camera placement, use the displayed coverage visualization. Check that later walls, tall fixtures, or decorative objects do not compromise the intended view, and verify the live security score after installation.

High-value businesses may require simultaneous guards during all open hours, with the exact live requirement depending on type, size, equipment, and skill. Reserve the guard locker or required support object in an accessible employee zone. Staffing is not a substitute for camera and panel coverage.

Create a cleaning route that reaches every public area without forcing the cleaner through a permanent checkout queue. Place cleaning equipment where it is valid and accessible but does not narrow the delivery path.

If an interior installation service placed cameras and coverage does not register, a current developer troubleshooting reply suggests removing and replacing affected cameras can refresh recognition. Reproduce the issue on build 3674 and report it if the score remains inconsistent.

Evaluate security economically but never create an intentionally invalid layout to save wages. Read theft in the store’s EconoView, compare avoided loss with guard cost, and shorten hours or rethink the product mix if the required protected tail is unprofitable.

Blueprints, duplication, and controlled reuse

Blueprints save labor only when the receiving premises and business requirements truly match. Standardization needs a validation gate.

Official EA 0.9 notes introduced the Blueprint Creator for saving complete layouts with furniture and settings. Later versions expanded placement tooling. In 1.0, use a blueprint as a starting configuration, not proof that every current requirement is satisfied.

Label each blueprint with business type, shell code, intended target T, build, required products, staffed lanes, storage capacity, and security assumptions. A name such as ‘clothing 30’ is incomplete if it omits whether every current category and employee demand is covered.

Before installation, compare doors, delivery spots, wall geometry, and building type. Workshop filters expose shell and business categories, but a community upload can be stale, mod-dependent, overbuilt, or tuned for aesthetics. Read its contents rather than trusting popularity.

After installation, walk the full customer and delivery journeys, open the business status screen, validate every workstation, inspect camera coverage, count storage, and run off-site and on-site tests. Do this before hiring a maximum roster.

When improving a standard, save a new version rather than silently overwriting the evidence label. Keep the old layout long enough to compare cost, capacity, and pathing. The most useful blueprint library is small, documented, and reproducible.

Expansion and retrofit decisions

Add capacity only where repeated evidence identifies the limiting stage. More furniture everywhere increases cost and clutter without necessarily adding a customer.

Use the hourly graph and on-site observation to locate saturation. If realized customers repeatedly equal a specific capacity while price satisfaction, demand, promotion, and stock are healthy, that stage is a candidate for expansion.

Calculate the incremental package: purchase and installation cost, floor space, added stock, additional worker wages, security coverage, and lost circulation. Compare expected added contribution with that package. A fixture that raises a theoretical cap but displaces a queue pocket may reduce physical performance.

Change one stage at a time when possible. Add one staffed register during peaks, one set of required product fixtures, or one service desk, then rerun the same weekdays. If several items are required together, label the experiment as a bundled expansion.

Relocation is appropriate when the premises cap is the repeated minimum and demand can support more, or when the shell cannot physically hold a balanced chain. Do not move merely because a larger address exists; estimate rent, installation, downtime, logistics, and staffing deltas.

Scenario: every product and register supports 40 customers but the premises limit is 30 and the graph repeatedly reaches 30. Additional fixtures cannot lift that store. Compare margin optimization with the full cost of moving to a higher-capacity shell.

Layout troubleshooting decision tree

When sales underperform, distinguish missing requirements, capacity bottlenecks, physical pathing, supply, staffing, and market conditions before rebuilding.

Node one: does the business status screen show a missing or invalid requirement? If yes, use F1 and the item placement information to correct it. Do not continue to market analysis while the business is mechanically incomplete.

Node two: is the hourly graph flat at a known limit or are there queues? Compare building, required-category, transaction, service, seating, production, and staffed capacities. Upgrade only the smallest relevant stage.

Node three: are results worse only while the player is present? Observe entrance, aisles, queues, chairs, doors, and exits. Clear the first reproducible collision, then retest both present and simulated operation.

Node four: is a display empty or delivery failing? Check total store stock, combined display capacity, logistics target, warehouse source, destination storage, box size, and delivery timing. Repair supply before moving sales fixtures.

Node five: are all operations healthy but customers remain low? Inspect MarketInsider’s correct neighborhood, demand, providers, traffic, promotion, price satisfaction, and opening hours. The layout is not the cause of every low customer count.

Management record and final audit

A layout should leave behind an auditable capacity map, not just a screenshot. The final record makes later patches, expansions, and repairs much faster.

Record premises code, business type, build, tested target T, opening hours, and whether tests were on site or off site. List every capacity-bearing stage with placed count, live capacity per object, combined capacity, staffed count by peak, and observed saturation.

For inventory, record each SKU or category, assigned fixtures, combined display units, store target, reserve boxes, delivery cadence, and route. For support, record cleaning station, bathroom, baskets, security score, cameras, detectors, guard support, and employee-demand objects.

Capture the floor plan with entrance, delivery spot, customer loop, queue pockets, storage, and workstation faces marked. A plain annotated sketch is more useful for diagnosis than a polished image without interaction directions.

Pass the operational audit: no requirement warnings; every workstation assignable; every route traversable with a hand truck; no entrance or queue blockage at peak; current security recognized; storage accepts the next delivery; simulated and player-present results are coherent.

Pass the economic audit: the chosen target is supported by observed demand; active payroll follows peaks; stock survives the replenishment interval; added capacity earns more contribution than it costs; and any reusable blueprint is labelled with build 3674 and its assumptions.

Perform a change-control walk before declaring the design final. Move through the premises in the same order as a delivery worker, a customer, a cashier or specialist, a cleaner, and a guard. For each role, note its starting point, destination, interaction face, narrowest passage, queue conflict, and return route. Repeat once during a proven busy hour and once with the business closed for restocking. This role-by-role pass often reveals that an object is technically valid yet operationally awkward.

Finally record a rollback point. Save the prior blueprint name, installation cost, furniture moved, stock displaced, and the last valid performance week before a major retrofit. If the new layout lowers customers, creates warnings, or breaks player-present flow, compare the exact capacity map rather than improvising more furniture. Restore or revise only the changed zone. A reversible experiment protects both cash and diagnostic clarity, especially in a large store where multiple small obstructions can look like one general demand problem.

Add a peak-load acceptance test with a written threshold. Select a weekday-hour that previously produced the highest valid traffic, arrive before the peak, and observe at least one complete customer cycle. Count arrivals, completed transactions, maximum queue, blocked-path events, idle staffed stations, empty required fixtures, and employee detours. Then leave the premises and compare the next equivalent off-site hour. Pass only when both modes agree closely enough for the store’s operating purpose and every difference has a documented explanation. This final test catches layouts that satisfy static capacity labels yet fail under simultaneous customer, employee, cleaner, and replenishment movement. Record the observation date and repeat it after any structural change.