VIN and model search
A buyer finds a part by VIN number or by picking the vehicle's make, model and year.
E-commerce · Mobile + web platform
ZipIt is an auto parts marketplace and a CRM for sellers. The app aggregates parts from many stores and helps buyers find the right part fast by VIN, make and model, while the web CRM gives sellers control over stock, outlets and sales.

In short: what the product is and who we built it for.
ZipIt is two products built around one dataset: a buyer app for iOS and Android, and a web CRM for sellers. A buyer searches for a part by VIN or by vehicle make and model, compares offers from different stores and builds one order out of them. A seller in the CRM manages their outlets, runs a stock, receives incoming goods and tracks the store's finances.
The client, a car rental business, had run into the complexity of buying parts from many suppliers. The task was to build a marketplace that aggregates offers from stores and lets buyers find the right part quickly, while giving the back office a CRM to manage the catalog and listings.
The auto parts market is fragmented: dozens of independent stores sell parts, each with its own range, prices and stock. Buyers had to call sellers one by one and match part numbers by hand, and compatibility with a specific car was judged by eye, with a high risk of ordering the wrong part.
Sellers, in turn, lacked a single tool for bookkeeping: outlets, stock, incoming goods and finances were tracked separately. The task was to bring supply and demand together on one platform and give sellers a back office for managing their range and sales.
How we built the product, from architecture to process.
We split the product into two roles: the buyer works in a mobile app built on Flutter, the seller works in a web CRM built on React. Both rely on a shared backend on PHP Symfony and a single auto parts catalog, so a store's stock and prices are visible to the buyer right away.
In the app we focused on speed of finding a part: passwordless SMS login, search by VIN or by make and model through the user's garage of vehicles, and side-by-side comparison of originals and aftermarket parts from different sellers. In the CRM we covered the seller's full cycle: outlets, a stock with goods receiving, the product range, sales and store finances with payouts.
Tools chosen to fit the product’s goals.
A Flutter mobile client gives one codebase for Android and iOS: it speeds up development and keeps releases in sync. For a marketplace with search and a personal account, that means the same UX on both platforms without duplicate code.
We considered the alternatives: two native apps (Swift/Kotlin give full API access but double the build cycle) and React Native (fast to start, but limited access to native camera/GPS modules). Flutter was chosen for a single code cycle and fast releases on both platforms.
Key capabilities that solved the business problem.
A buyer finds a part by VIN number or by picking the vehicle's make, model and year.
Items from several sellers are combined into one order; delivery cost depends on the store.
Fast sign-in to the app by phone number and an SMS code, no password needed.
A seller sets up stores and warehouses; deleting an outlet moves its items to a 'Temporary warehouse'.
Inventory tracking, receiving items one by one or via an Excel upload, write-offs and per-outlet availability.
Balance, sales, fines and top-up operations, and payouts to the seller's account.
Key product screens, step by step.




The app's start screen opens with the headline 'Find and get auto parts delivered in Kazakhstan' and invites the buyer to add a car to their garage for faster part lookup.
From there the buyer picks a search method straight away — by VIN number or by make and model — and moves into the catalog. The bottom navigation leads to home, catalog, cart and profile.
Signing into the CRM starts with registering a store (company name, country, city, contact details and agreement to the terms), followed by login with a phone number and password.
In a separate step the seller sets a login password with a complexity requirement — Latin letters and at least one digit. That gives the seller an account and access to the store's management panel.
In the 'Outlets' section a seller sees a list of their stores with name, address and a note, and creates new outlets in a modal window with address search.
Deleting an outlet is protected by a confirmation: if items are linked to it, the system warns that they will be moved to the 'Temporary warehouse' section so listings are not lost.
The 'Stock' section is a table of items with part number, manufacturer, price and quantity, with search, a filter by outlet and an availability toggle at the top.
A dropdown list of outlets lets a seller view balances for a specific store or for the 'Temporary warehouse', while 'Receive' and 'Write off' actions track every stock movement.
Clicking a line item opens the item card: photos, name, manufacturer, part number, sale price and average purchase price, quantity and outlet.
The same card sets availability on request, delivery time and warranty — the terms a seller defines that a buyer then sees in the app.
Receiving starts from the product list: a seller finds an item, fills in the outlet, purchase and sale price and quantity, then adds it to the receiving list.
An alternative to manual entry is uploading a list of items from an Excel file using a ready template. The compiled list is confirmed with the 'Receive items' button.
In the 'Account' section a seller sees the company's details and an offer to verify the account to get access to selling on the marketplace.
Verification runs through several checks — taxes, court cases, reviews, recommendations — with clear status indicators. After a successful check, the screen 'Your account is verified!' appears.
The 'Finances' section shows the store's balance and lets a seller withdraw or top up funds, as well as open the operations log.
In 'Operations' a seller filters movements by type (sale, top-up, withdrawal, fine) and status, and when withdrawing enters an amount and chooses a receiving account — the platform records every operation.




Signing into the app is built without a password: the buyer enters a phone number, agrees to the terms and privacy policy, and receives an SMS code.
The 'SMS code' screen handles every state — waiting for input, a timed resend, and the error 'Incorrect code' — so sign-in stays quick and clear.




Part search starts with selecting a vehicle: the buyer enters a VIN/frame number or goes into 'Search by parameters'.
There they pick a make from a list with brand logos, then the market, model and year of manufacture — moving straight to parts compatible with their own car.



On the part card a buyer sees photos, price, installment options, the seller with a rating, delivery terms and specs — brand, OEM number, quality (original), warranty, country of manufacture.
Before adding to cart, a quantity and store selector opens: each seller has their own stock, price and delivery cost, so the buyer can put together the best combination.
At checkout the buyer enters a delivery address and sees items grouped by store, a subtotal per seller and an order comment before moving to payment.
After checkout the order appears in tracking with the status 'New', a date, address and contents, and the seller gets a notification about the new order in the CRM.
The apps collect users' personal data (name, phone, delivery address). The payment flow runs through an external payment gateway, and card data is never stored on ZipIt's own server.
Personal data is processed under the requirements of the client's jurisdiction, with role-restricted access for sellers and protected handling of store finance records.
Two products in one project: an Android/iOS marketplace app and a web CRM for sellers.
Fast auto parts search by aggregating offers from different stores.
A seller account with login and listing management.
Multiple outlets for one seller with unified tracking in the CRM.
Agile to Scrum: discovery and sprints covering both products.
Stack: PHP Symfony + React (CRM), Flutter (Android/iOS).
The cost depends on the set of integrations (parts catalog, payment gateway, delivery), the number of platforms and the requirements for handling personal data. We give a precise estimate after reviewing the brief.
A CRM covers back-office tasks that off-the-shelf tools don't: a parts catalog, stock tracking across several outlets, price management and sales reporting.
A user enters a part name or picks a category from the catalog. The marketplace pulls in matching items from every connected store by that part number.
Buyers' personal data (name, phone, address) is stored on the operator's server. Payment details are processed through an external gateway, and card data is never stored on the platform. The data is handled under the requirements of the client's jurisdiction.
The typical range for a cross-platform app with a web back office is 16–24 weeks. The exact range depends on the number of integrations and the complexity of the business logic, and is fixed after discovery.
Companies from retail, medtech, logistics and e-commerce that we helped build digital products.
The full spectrum of development — from native mobile apps to web platforms, AI and cloud. Pick a direction or order a turnkey project.
Native iOS & Android plus cross-platform Flutter and React Native — from MVPs to apps with millions of installs.
Learn moreNative Swift / SwiftUI iOS apps — with Apple Pay, Sign in with Apple, App Store Connect deployment pipelines.
Learn moreNative Kotlin / Jetpack Compose Android apps — Material 3, Google Play release pipelines, Firebase integration.
Learn moreSingle Dart codebase across iOS, Android, web and desktop — with native modules where needed.
Learn moreProduction web apps on React, Next.js, Vue and Node — SaaS dashboards, B2B portals, marketing-conversion stacks.
Learn moreREST, GraphQL and gRPC APIs — designed for partners, mobile clients and internal microservices.
Learn moreBespoke platforms for mid-market and enterprise teams — internal tools, vertical SaaS, mission-critical backends. Discovery to launch in 12–36 weeks.
Learn moreFocused MVPs in 12–20 weeks — one or two integrations, real users on day one, telemetry built-in.
Learn moreEnd-to-end ownership of a digital product — design, build, ship and continuous evolution.
Learn moreTool-using agents that plan, retrieve, act and self-evaluate — in customer service, ops automation, internal copilots.
Learn moreAWS, Azure and GCP architecture, Kubernetes, Terraform/Pulumi, CI/CD and observability — SRE-grade operations for product teams.
Learn moreTechnical SEO, Core Web Vitals, structured data, internal-link architecture — built into your engineering process.
Learn moreRelated cases

Local marketplace mobile app for an offline children's-goods chain — flexible catalog, two-tap checkout, online/offline stock sync.
View case
Retail POS companion app for a multi-brand boutique chain — ElasticSearch cross-store inventory search, 1C-system integration.
View case
B2B e-commerce and product configurator for a global polymer manufacturer with multi-region pricing, stock and dealer workflows.
View case20 articles across 5 categories — engineering-led guides on AI, SaaS, MVP, compliance and mobile for US and EU product teams.

Performance-tested comparison of RN (New Architecture) and Flutter (Impeller) across hiring, time-to-market and EU/US compliance.
Read article
Real cost ranges by region (US onshore, Western EU, EU nearshore), team and feature scope. With a worked fintech example.
Read article
Data-driven framework for choosing iOS-first or Android-first in 2026 — US & EU market share, ARPU, review timelines, EU DMA.
Read articleTell us about your suppliers and your sales process, and we will help you design a marketplace that aggregates offers and gives sellers a working back office. Let's discuss how a similar platform could work for your business.
Share a few details and a senior consultant will reply within one business day.
Email: sales@yusmpgroup.com
Phone: +374 44 871 811
Offices: KAMAR Business Center, Vazgen Sargsyan St. 2, Yerevan, Armenia · Remote — East-Coast US overlap (9 AM–1 PM ET)