Icolan.ir

A Persian Laravel commerce platform covering mobile discovery, customer accounts, cart and checkout, ZarinPal payment, orders, fulfilment, product feeds, SEO, and media migration.

icolan.ir
Storefront and product discovery · Live website capture
Year
2026
Role
Commerce engineering
Scope
Laravel · Checkout · Operations
Status
Live

The project, in context

I designed and developed Icolan around the full order journey: finding a product, choosing its variant, paying, following delivery, and returning for support. Its Persian Laravel storefront shares a product and order foundation with administration, customer relations, fulfilment tools, and editorial content.

A purchase has a long tail

A storefront can look convincing while the work behind it remains fragmented. Product variants, stock, discounts, shipping records, and customer questions all affect the same purchase. If they are treated as separate tasks, the shopper sees inconsistent information and the team repeats work across tools.

Persian commerce also brings very practical constraints: mobile screens, right-to-left reading, mixed Latin product names and numbers, and shipping PDFs whose text extraction may be imperfect. The platform needed to address these details without pushing operational complexity into the customer's path.

One order, shared context

The Laravel application connects discovery, product detail, cart, checkout, and the customer account to one product and order model. Search and catalogue controls support browsing, while the product page carries variants, availability, questions, reviews, and restock requests. After purchase, order history and tracking keep the next step visible.

Administration covers products, media, orders, content, and store health. Fulfilment has its own import and print tools, and CRM separates customer follow-up from public browsing. Public screenshots demonstrate the storefront; the private capabilities described here are implemented in the application and are not presented as customer data or open-access screens.

What I built

The parts that make this project useful in day-to-day work.

  1. Discovery that respects intent

    The catalogue supports category and collection browsing, text search, in-stock filtering, and price sorting. Search suggestions shorten the route to a product, while search insight records help the team see what visitors ask for and where results are missing.

  2. Product detail with useful choices

    Product detail includes variant selection, stock and price context, product questions, reviews, and restock requests. Wishlist, comparison, and recently viewed products support a purchase that may take more than one visit instead of forcing an immediate decision.

  3. Cart, checkout, payment

    Cart quantity updates and coupon handling lead into checkout and the ZarinPal callback flow. Orders have their own state rather than being inferred from a front-end success message. Delivery details can continue into the customer account and the team's order screen.

  4. An account that continues the service

    The account includes order history, order detail, reordering, profile changes, notification reading, and support tickets with conversation history. Password and session controls have a dedicated place, keeping account maintenance separate from shopping actions.

  5. Fulfilment with less re-entry

    Fulfilment tools include dispatch manifests, batch printing, and importing Postex PDF shipment records. The parser normalizes extracted text, handles malformed UTF-8, and groups records by tracking code. Public tracking exposes a customer-facing route without opening the administration interface.

  6. Customer follow-up and store control

    Administration brings product and category editing, stock and order work, content publishing, and customer follow-up together. The CRM adds tasks, message templates and campaign queues, while accounting and wholesale invoice screens support the operational side of the business.

  7. Content and search foundations

    The magazine and product video archive extend product understanding. Technical routes include sitemap, robots, product feeds, and a Torob integration endpoint. SEO health, search insight, and web vital collection give administrators concrete signals to inspect rather than a generic optimization label.

From structure to release

  1. Map the purchase

    The interface follows the purchase from discovery to delivery, with explicit states for selection, stock, checkout, and orders.

  2. Connect the back office

    Product, order, customer, and shipment records give different team screens a shared reference instead of isolated copies.

  3. Handle real input

    Persian PDF extraction and catalogue queries receive specific handling, including text normalization and availability-aware price sorting.

Delivery and current scope

  • Persian Laravel storefront, catalogue, product detail, cart, and checkout.
  • Customer accounts, order history, tracking, and support conversations.
  • Product and order administration, CRM, shipment imports, and print tools.
  • Magazine, media pages, product feeds, and technical search routes.

Questions about this project

What was built for Icolan?

A Persian Laravel commerce application with connected storefront, customer accounts, administration, CRM, and fulfilment tools. Its scope includes the work after checkout as well as the public buying experience.

Can customers follow an order?

The application provides order history in the customer account and public order and shipment tracking routes. These are customer-facing paths, separate from the staff's shipment administration.

What can the sales team manage?

The staff interface covers product and stock management, orders, dispatch lists, batch printing, and shipment imports. Customer follow-up, tasks, message templates, accounting, and wholesale invoice screens support the work around each purchase.

Have a similar project in mind?

Tell me what you need to build and where the current experience falls short.

Next projectDrZerafati.ir