Shoppergetit - Urban Retail Infrastructure

What Shoppergetit Is

Urban retail infrastructure for predictable distribution. Shoppergetit connects local retailers, customer demand, and fulfilment through one intelligent commerce system.

The Insight

Cities already have retailers, inventory, and demand. What is broken is how fragmented those pieces are.

• Retailers
• Inventory
• Customer demand

The Traditional Constraint

Commerce growth can create increasing dependency on warehousing, owned inventory, operational labour, and fulfilment complexity.

The Shoppergetit Model

Shoppergetit coordinates inventory already held by local retailers instead of building growth around increasingly expensive warehouses and owned inventory. Technology, AI, and automation coordinate retailer inventory, product digitisation, customer demand, quality control, transactions, customer engagement, fulfilment, and operational workflows.

Design Principle

More customers shouldn't require more warehouses and more people. Shoppergetit is designed so customer growth does not require warehouse and headcount growth to increase proportionally at the same rate.

Traditional Inventory-Heavy Commerce Expansion

• More Customers
• More Owned Inventory
• More Warehousing
• More Operating Headcount
• Higher Fixed Operating Burden

Shoppergetit

• More Customers
• Existing Retailer Inventory
• Technology-Coordinated Demand
• Automated / Quality-Controlled Operations
• Greater Transaction Density

Context

Shoppergetit is a Pendulum HQ subsidiary and urban retail infrastructure venture for predictable distribution. It connects local retailers, customer demand, and fulfilment through one intelligent commerce system.

Problem

Cities already have retailers, inventory, and demand. The problem is fragmentation: product information, demand capture, transaction flow, quality control, fulfilment, and customer engagement often sit in disconnected places.

My Role

As Co-Founder and Technical Product Lead, I shaped the opportunity, product model, workflows, priorities, and release decisions within the Pendulum HQ ecosystem. I translated marketplace requirements into experience and system logic, supervised technical execution, and aligned product decisions with capital and launch realities.

Constraints

• Coordinating inventory already held by local retailers without requiring Shoppergetit to own that inventory itself.
• Balancing three operating surfaces: shopper, retailer, and admin workflows.
• Shipping under early-stage capital, team, and go-to-market constraints.
• Supporting quality control, fulfilment, customer engagement, and operational exceptions without creating avoidable manual burden.

Product Decisions

Execution Process

• Mapped critical shopper, retailer, admin, logistics, and exception journeys.
• Defined release priorities around transaction confidence and operational control.
• Directed UX architecture and requirements across marketplace workflows.
• Worked with implementation decisions across a Next.js, Node.js, MongoDB, and Redis stack.
• Used analytics instrumentation and launch learning to inform subsequent product decisions.

Technical / System Thinking

Shoppergetit is a coordination system. Existing retailers hold inventory; customers create demand; the platform digitises products, controls quality, coordinates transactions, supports fulfilment, and gives operators the workflow visibility needed to keep the system predictable.

Product Screens

Selected product and workflow views from this work.

Lessons Learned

• More customers shouldn't require more warehouses and more people.
• Retail distribution becomes more scalable when existing inventory can be coordinated instead of duplicated.
• Early role clarity across admin, retailer, and shopper experiences reduces manual firefighting later.
• Product leadership in a constrained startup requires prioritizing system integrity and commercial learning at the same time.