Alikolo
Alikolo was an Indonesian e-commerce marketplace where sellers could list products and buyers could purchase items for delivery, including remote destinations. It tried to attract demand with free shipping, but sales dropped when the promotion stopped. The case is about unclear differentiation, weak founder control, and dependence on funding to scale.
View sourceProduct snapshot
What it was
Let sellers list products in an online marketplace, let buyers purchase them, and arranged delivery to customers.
Who it was for
Problem / value
Make online buying and selling easier in Indonesia, especially when delivery was part of the problem.
Core workflow
Sellers list products, buyers purchase through the marketplace, and the platform coordinates delivery to the destination.
Core dependency
The model depended on shipping economics, buyer trust, seller supply, and continued funding.
Product form
Pricing model
Sales were helped by free shipping; Failory says sales dropped significantly when the shipping promotion stopped.
Competitors or alternatives
What happened
Summary
Alikolo appears in public Failory material as an Indonesian e-commerce marketplace. The source record is limited, so the case should be used to test marketplace positioning, demand clarity, and distribution assumptions rather than to claim a detailed cause of failure.
Outcome
Alikolo is treated here as a low-confidence archived marketplace risk signal based on available public sources.
Core risk
Broad marketplace before a clear buyer and seller wedge
Shutdown reason
No single verified shutdown reason is available from the linked public material; the useful builder risk is building a broad marketplace before proving a sharp buyer reason and seller wedge.
Timeline
- The product was positioned as an e-commerce marketplace in Indonesia.
- The marketplace category required both seller supply and buyer demand against existing alternatives.
- The product appears in public cemetery/failure material, but the public record does not provide a full founder postmortem.
Before you build
Why it matters
This matters for builders entering e-commerce categories. A marketplace needs a reason for sellers to list and a separate reason for buyers to switch; building the platform does not create either side automatically.
Primary check
Start with one buyer-seller wedge, prove repeat transactions, and validate acquisition in a narrow e-commerce category.
Checklist
- Run one manually curated category before adding marketplace features.
- Measure repeat purchases from a small buyer group.
- Pre-sign sellers with inventory that buyers cannot easily find elsewhere.
- What narrow category gives the marketplace an unfair start?
- Why would sellers join before demand is large?
- Why would buyers choose this marketplace over existing options?
Relevant if
- You are building a broad marketplace with many seller or product categories.
- Your differentiation is not specific enough for one buyer segment.
- You have not proven repeat transactions in one narrow niche.
Less relevant if
- You already control a unique supply source that buyers actively seek.
- You are starting with one niche and have repeated transactions before platform buildout.
Pre-build tests
- Operate the first category through chat, spreadsheets, or a simple storefront.
- Test one acquisition channel for buyers and one for sellers before platform work.
Transferable lessons
- Choose one category where supply or buyer pain is unusually strong.
- Validate why sellers would join before there are many buyers.
- Validate why buyers would switch before there is broad inventory.