Get a quote

E-Commerce · Izmir

E-Commerce for Izmir businesses

Producers around Izmir rarely sell one size of anything. In food and agriculture catalogues the same item comes back in several volumes or gram weights, and that repetition is where the catalogue knot sits. Open a product per size and the list fills with duplicates; merge the sizes and stock stops being countable per size. On Kokudankokuya we drew the variant boundary at bottle size: the fragrance stays one product record, while price and stock hang off the size.

E-Commerce — Izmir

Izmir sits at the centre of the Aegean producer and trading economy, where firms making food, agricultural goods and machinery can put their own catalogues online instead of selling only through intermediaries. A producer catalogue has a shape of its own: the same item repeats across sizes, a buyer may search without knowing the brand, and whoever keeps the listing current works inside the producer's own team. Kokudankokuya is the closest thing in our portfolio to that shape, and it answers all three points: a size becomes a sellable unit rather than a second product, fragrance family and notes open a second navigation axis beside the category tree, and the catalogue's scale never called for a separate search or cache layer. The store runs on Laravel and MySQL, and the fewer parts there are to move, the more realistic it becomes to leave catalogue maintenance with the producer's own staff.

  • The variant boundary is drawn at bottle size: the fragrance stays one product record, price and stock hang off the size, and adding a size does not add a product.
  • A second navigation axis runs beside the category tree, so a shopper who knows no brand names starts from the character of a scent, and one perfume attaches to several notes instead of sitting in a single branch.
  • The store rests on few parts, because the catalogue's scale did not call for a separate search or cache layer, and the surface a maintaining team picks up stays small.

Why Algoriel

  • Priced by your own unit

    If you do not sell by the piece, the records do not either: Kokudankokuya prices and stocks every volume on its own.

  • Price moves with the choice

    Trim and colour update the price on the same screen, so a buyer never opens the basket just to see a total.

  • Used stock is a filter

    New and used machinery share one listing on Plastik ve Makina, with condition as a filter instead of a second catalogue.

  • One flow through to payment

    Configuring a product and paying for it are two steps of the same flow, with no handover to another system.

What we build

E-Commerce
  • The storefront

    The shop window, product pages, search and navigation follow how your customers actually look for what you sell. At Kokudankokuya the scent family and its notes open a second route beside the category tree.

  • Configuration into checkout

    When a sale needs choices and prices moving together, payment becomes the last step of that same flow rather than a separate form. On the KGM SsangYong sales channel the price updates on screen as the buyer picks trim and colour.

  • Variants and pricing

    Price and sales conditions attach to the unit you actually sell, so a customer never rebuilds a configuration at the next step. The KGM SsangYong sales channel stores every trim and colour pairing with its own price and its own image.

  • Inventory and operations

    Stock and order information is tracked the way your team already works. Kokudankokuya keeps a scent as one product record while each volume is its own sellable unit, so adding one never means opening another product.

  • Only the parts the job needs

    We do not assume your traffic and add layers for it, because you are the one who maintains them for years. Kokudankokuya's catalogue never reached a scale that called for a separate search layer.

  • Payment and shipping connections

    The payment and shipping providers you already use connect at the same point in the sales flow. You choose who you work with, and the connection is built around that choice.

Work like this

E-Commerce · Case study

Kokudankokuya — bottle size as a variant, not a second product

The same fragrance sells in several bottle sizes — opening each size as its own product bloats the catalogue with repetition, while collapsing them into one loses stock and pricing per size. We set the variant boundary at size: the fragrance stays a single product record, price and stock hang off the size, and adding a size does not add a product. Fragrance family and notes sit beside the category tree as a second navigation axis, so a buyer who does not know the brand name starts from the character and arrives at the product.

Read the case study →

Working with Izmir teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • We sell the same product in several sizes. How does the catalogue carry that?

    The variant boundary goes underneath the product, at size. On Kokudankokuya the fragrance is one product record while each bottle size carries its own price and its own stock, so a new size is a variant definition rather than a second listing to keep in step.

  • We want to sell to buyers abroad. How do you approach that?

    The catalogue structure does not depend on where the buyer sits — product, size, price and stock stay in one model. The payment and delivery side of a cross-border order is something we scope before promising it, because which provider belongs on which line follows from the terms you already trade under.

  • Can our team manage products and content themselves?

    It depends on where the rule lives. On Kokudankokuya, adding a bottle size means defining a variant rather than opening a second product record. On Vipkurum an institution picks how its own exam is scored from the management layer instead of waiting for a release. We keep decisions of that kind out of the codebase.

  • Do you work remotely?

    Yes — the whole engagement runs remotely, from the scoping conversation through to handover. We also build the store so it can be handed back: with few parts to keep running, the catalogue can stay with a producer's own staff rather than depending on us.

Let's plan your catalogue and your checkout.