Get a quote

E-Commerce · Umraniye

E-Commerce for Umraniye businesses

On the industrial side the buyer is often the same firm while the job behind each order keeps changing. If you are a mechanical contractor around Dudullu in Umraniye, you may order for several separate sites inside one month. If the basket hangs off the buyer alone, those jobs merge into a single account history and nobody can later say which line went to which site. Calculator Resterm was built around that: the basket hangs off a project, and the project hangs off that project's customer.

E-Commerce — Umraniye

Umraniye's texture is the Dudullu industrial estate, where small manufacturers, mechanical contractors and air conditioning firms form different links of one supply chain. In a chain like that the online selling question is not shelf layout but record layout: if a line does not carry which job it belongs to, the month-end question of who bought what for which site has no answer. The work closest to this district's profile is Calculator Resterm. Where it does not overlap is plain — that is a manufacturer's own selection and quoting software rather than a retail store, and we have nothing to show for shipping, returns or marketplace integration. The core is in Laravel, the records in MySQL, the calculation screen in Vue. The team is fully remote.

  • The basket hangs off a project rather than the buyer, so two jobs for the same firm never dissolve into one account history.
  • The input is a heating requirement rather than a product code, and the engineering calculation picks the electric heater instead of a person scanning a catalogue.
  • What the calculation produces becomes the commercial line directly, leaving no spreadsheet between the technical choice and the sales record.

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

Calculator Resterm — the basket hangs off a project, not the buyer

Resterm manufactures electric heaters. The input is a heating requirement, not a product code: the software runs the engineering calculation and picks the heater. The chosen heater drops into a basket, the basket attaches to a project, and the project to that project's customer, so separate jobs for one buyer keep separate records. The calculation's output becomes the commercial line, with no spreadsheet between the technical choice and the sales record. It sits on the manufacturer's own product structure. Laravel at the core, MySQL for records, Vue for the screen.

Read the case study →

Working with Umraniye 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

  • One customer orders for several construction sites. How do the records stay apart?

    The basket attaches to a project rather than to the customer. Each job carries its own project record, and the project attaches to that project's customer, so two jobs for one firm never dissolve into a single account history.

  • Our product is not a heater. Does the calculation step transfer?

    What transfers is the sequence, not the heater: a requirement goes in and a sellable line comes out. Whichever quantity decides the product is what the calculation is built on. At Resterm we built it on the manufacturer's own product structure rather than loading a catalogue into a ready-made tool.

  • Can you connect us to marketplaces and shipping companies?

    We did not build that side on Resterm. We have nothing to show for shipping, returns or marketplace integration, so we promise none of it. What we describe is the chain that runs from a selection to a sales record.

  • Would you not need to come to Dudullu and map our product tree on site?

    We keep no office and send nobody to a site; the work runs fully remotely. A product tree comes out of settling which input picks which product, which is a table exercise rather than a visit.

Let's plan your catalogue and your checkout.