Choose 4, 6, 8, 12, 16 or 24 slots by the venue's observed demand, the battery buffer needed between replenishment visits, maintenance access and the stage of the pilot. Slot count should follow operating evidence, not replace it.
For a first controlled pilot, 6 or 8 slots usually provide a practical balance between footprint and operating buffer. Twelve slots fit venues with steadier turnover; 16 and 24 slots suit higher-capacity plans only after demand and servicing can support them. A 4-slot compact selection remains model-confirmation-required in the current catalog.
These are operating patterns, not demand forecasts. Confirm the selected model, dimensions, power input, protocol and market requirements before ordering.
| Slots | Typical use | Operating signal | Replenishment and maintenance | Evidence route |
|---|---|---|---|---|
| 4 | Very compact concept or constrained counter test | Use only when a small footprint matters more than battery buffer | Frequent attention may be required; exact public model is not confirmed | 4-slot selection |
| 6 | Small venue pilot and staff-visible counter placement | Useful when the team wants a limited first batch and clear replenishment routine | Compact service load; monitor unavailable-battery periods | 6-slot models |
| 8 | Balanced pilot for venues needing more buffer | Choose when 6 slots may turn over too quickly but a larger station is excessive | Moderate refill buffer without a large footprint | 8-slot models |
| 12 | Steadier venue demand or multi-period traffic | Use when observed rental and return patterns support more available batteries | Plan access, fault isolation and refill responsibility | 12-slot models |
| 16 | Higher-capacity station planning | Use product-catalog models only after footprint and service assumptions are verified | No standalone 16-slot detail page in this release | 16-slot catalog filter |
| 24 | High-traffic venue plan with a larger inventory buffer | Consider after demand, return availability and staff support are demonstrated | Requires an explicit refill, fault and exception process | 24-slot models |
The same method can be used before a pilot and again after the first operating review.
Record dwell time, operating hours, counter or floor space, staff access and how often an operator can visit.
Decide how many charged batteries should remain available between visits. Do not convert traffic assumptions into guaranteed rentals.
Confirm where users can return, who moves batteries between venues and how unavailable or faulty slots are handled.
Check dimensions, weight, power input, communications, screen or label options, protocol compatibility and source fields in the product catalog.
Compare completed orders, unavailable-battery periods, return exceptions, support records and venue participation before choosing a larger format.
A larger station does not guarantee more demand or lower operating cost. Current product materials do not establish a public A/B factory-to-slot-to-model allocation. Four-slot model details remain pending confirmation.
Answers use the current public product catalog and avoid unsupported demand, inventory or certification claims.
A compact 6 or 8-slot station is often easier to replenish and observe in a controlled pilot, but the choice should follow venue dwell time, expected turnover, staff access and the desired battery buffer. A 4-slot format requires model confirmation before procurement.
Consider higher slot counts when observed demand, unavailable-battery periods and replenishment workload show that a compact station cannot maintain the intended buffer. The 16-slot options are documented in the product catalog, but CoreCharge Cloud does not publish a separate 16-slot detail page in this release.
No. Slot count provides inventory capacity, not demand. Venue traffic, dwell time, renter instructions, payment readiness, returns, replenishment and support still determine whether a location is workable.
Potential compatibility depends on the station protocol, firmware, device identity and agreed software scope. Confirm the exact model before assuming it can join the same operator account.
Send the venue types, expected service frequency and preferred slot range for a model and pilot-scope review.
