Skip to content

Commit

Permalink
phase 1 for introduction docs
Browse files Browse the repository at this point in the history
  • Loading branch information
filrak committed Feb 4, 2025
1 parent 9525deb commit e15359a
Show file tree
Hide file tree
Showing 6 changed files with 33 additions and 20 deletions.
26 changes: 15 additions & 11 deletions docs/content/guides/6.multistore/1.introduction/1.index.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,24 @@
---
title: Challenges with multistore setups
title: The problem
layout: default
---
# Challenges of multistore setups

# Challenges with multistore setups
## Adaptive setups are now more important than ever

Let's get started!
Markets and technologies evolve rapidly. Organizations must adapt quickly to stay competitive. Agility is not optional—it’s a core requirement for survival. The businesses that thrive are those that don’t just react to change but anticipate and embrace it.

::card{title="Next: How Alokai is uniquely positioned to solve this problem better than others" icon="tabler:number-1-small" }
New technologies emerge at an unprecedented pace, customer expectations shift constantly, and competitors are always looking for an edge. In this landscape, relying on static solutions or legacy systems is a liability. Companies that successfully integrate emerging innovations without disrupting operations gain a competitive advantage. The challenge is maintaining this adaptability while ensuring systems remain efficient and scalable.

#description
Businesses must now be built for continuous adaptation. Technologies evolve faster than ever, making adaptability the most valuable capability. Organizations must design their eCommerce infrastructure to be flexible, scalable, and integration-ready. A future-proof technology stack enables businesses to pivot seamlessly, staying ahead of market shifts and competitive pressures.

TODO
Companies investing in adaptable eCommerce solutions position themselves to iterate quickly, minimize technical debt, and maintain long-term scalability. Those that prioritize agility through technology will outpace competitors in efficiency and innovation.

## Challenges and hidden complexity of multistore setups

Scaling an eCommerce business across multiple brands, geographies, and touchpoints sounds like a natural next step. But the reality? It’s a logistical and technical minefield. As companies expand, agility often takes a hit—slowing down innovation, increasing overhead, and complicating operations.

Businesses often start with a single eCommerce platform, designed for a specific market and use case. Growth then happens through expansion into new touchpoints (mobile apps, marketplaces, social commerce), new geographies, or acquiring brands with their own tech stacks. Over time, what was once a streamlined setup becomes fragmented, introducing complexity that makes agility and scalability difficult.

How do you maintain speed and adaptability while managing multiple storefronts, integrating new acquisitions, and expanding into new markets? Let’s break down the key challenges and why solving them isn’t as straightforward as it seems.

#cta
:::docs-button{to="/guides/multistore/introduction/alokai-solve-this-problem"}
Next
:::
::
Original file line number Diff line number Diff line change
@@ -1,11 +1,9 @@
---
title: How Alokai is uniquely positioned to solve this problem better than others
title: The solution
layout: default
navigation:
icon: tabler:number-1-small
---

# How Alokai is uniquely positioned to solve this problem better than others
# How Alokai is uniquely positioned to solve this problem better than others.


::card{title="Next: Use cases" icon="tabler:number-2-small" }
Expand Down
15 changes: 13 additions & 2 deletions docs/content/guides/6.multistore/1.introduction/3.use-cases.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,23 @@
---
title: Use cases
layout: default
navigation:
icon: tabler:number-2-small
---

# Use cases

## Scaling to new touchpoints

Expanding to new touchpoints—mobile apps, marketplaces, in-store kiosks—seems like a logical step to reach more customers. However, without a unified approach, each addition introduces inefficiencies and fragmentation.

Take a retailer that starts with an online store and later launches a mobile app, an in-store kiosk, and integrates with third-party marketplaces. Each of these requires separate development, unique integrations, and individual maintenance. A simple feature update, like a new product recommendation engine, must be implemented separately across multiple platforms, leading to inconsistencies and slow rollouts. The website may get the feature first, while the mobile app lags behind due to separate deployment cycles, and the kiosk might not support it at all.

This disjointed approach also impacts debugging. A bug in a checkout flow might behave differently across platforms, forcing teams to troubleshoot in silos. Meanwhile, managing real-time inventory, pricing, and user sessions across these disconnected systems becomes increasingly difficult, leading to performance issues and degraded customer experiences.

Without a scalable, unified strategy, companies struggle with inefficiencies, longer time-to-market, and rising operational costs. Instead of focusing on growth, they are stuck managing an overly complex and fragmented infrastructure.

## Scaling to new geographies

## Launching new brands

::card{title="Next: Tooling and concepts" icon="tabler:number-3-small" }

Expand Down
2 changes: 1 addition & 1 deletion docs/content/guides/6.multistore/1.introduction/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Introduction
sidebarRoot: true
navigation:
icon: tabler:brand-nextjs
icon: tabler:number-1-small
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Tooling and concepts
sidebarRoot: true
navigation:
icon: tabler:brand-react-native
icon: tabler:number-2-small
2 changes: 1 addition & 1 deletion docs/content/guides/6.multistore/3.patterns/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Patterns
sidebarRoot: true
navigation:
icon: tabler:brand-nuxt
icon: tabler:number-3-small

0 comments on commit e15359a

Please sign in to comment.