Slim 01 / F91-D
5,000mAh · 20W wired · up to 15W magnetic wireless
Story: keep it thin enough for magnetic carry, but still make wired charging useful. The role is portability first, specifications second.
Buyer evidence note: Treat Slim 01, Multi X1 and Traveler 1 as separate SKU evidence sets; retail appearance is not verified sales volume.
Project snapshot: three G-TIDE formats mapped to retained ZEROSET project records: Slim 01 / F91-D, Multi X1 / F86-D and Traveler 1 / F82-C. Public G-TIDE and retailer pages are used only as current specification and channel cross-checks.
“Building three models was easy. Making sure they didn’t compete with each other was the harder part.”
Slim 01 takes the magnetic-portability role, Multi X1 handles everyday dual-cable convenience, and Traveler 1 focuses on AC travel charging. Mapping each need to a different mature platform keeps the range clear, while battery, charging path, CMF and packaging remain controlled per SKU.
Project records support the model mappings. Public brand pages are specification cross-checks, not proof of audited sales or manufacturing volume.
Retail context only: public listings show G-TIDE channel presence; they do not establish ZEROSET manufacturing volume or audited sales. Brazil: Magazine Luiza. Colombia: Falabella lists Slim 01, Multi X1 and Traveler 1. Price, stock and sales indicators are point-in-time data.
F91-D → Slim 01, F86-D → Multi X1, and F82-C → Traveler 1 in retained ZEROSET project records.
It is physical retail-packaging evidence for the Multi X1 program and is shown as project evidence, not as a claim about total sales volume.
They cross-check current public specifications and channel presence. They do not replace retained project records or prove audited manufacturing volume.
Slim 01 covers magnetic carry, Multi X1 covers dual-cable daily use, and Traveler 1 covers AC travel charging.
Battery configuration, PCB, charging protocol, cables, CMF, retail packaging and the compliance/document set should match the approved sample and project specification.
Yes, subject to engineering feasibility and IP boundaries. Buyers can start from current platforms or use Custom Development for deeper changes.
Use it as a portfolio-planning example: assign each SKU a clear role instead of building several products that compete on the same feature set.
Retail pages can show public channel context, while retained project records support the historical product mapping. Keeping the two evidence layers separate avoids overstating the manufacturing relationship.
See Factory & Quality Control and the Quality & Compliance Guide for the wider manufacturing and verification framework.
Target market, product role, capacity and power target, cable or plug layout, CMF, packaging, quantity and compliance requirements.
