EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

E-Commerce · Besiktas

E-Commerce for Besiktas businesses

Printed material outlives the offer it advertises: the card that goes into the box, the label stuck on the bag, the sticker in the glass. If your offer changes every couple of months the print stays put, and collecting material back once it has gone out is a cost of its own. Along the head-office stretch between Zincirlikuyu and Levent in Besiktas that decision is taken once, in the centre. QRVizit, the product we are building right now, looks straight at that gap.

Get a quote Tell us about your project

E-Commerce — Besiktas

Head offices and multi-brand corporate groups sit thick on the ground in Besiktas. If you prepare print once in the centre and send it out, pulling it back is expensive, and how much information a printed surface carries turns into a cost decision. We are building QRVizit now; we do not present it as finished and we give no delivery date. The part that does not overlap is plain: QRVizit is a business card product with no basket, no order record and no payment step, and hanging a store behind a campaign page is separate work. We have no agency or media client either. Underneath sit a Laravel core, MySQL records and a Redis cache, with Inertia and React on the interface.

  • The address on a printed surface outlives the offer: when the offer changes the card does not go in the bin, the page behind it is replaced instead.
  • Whoever scans the code downloads nothing; the camera opens the page directly, and we lay that page out to be read on a phone.
  • We keep the panel and the visitor's page inside one Laravel application, so changing content starts no second service that also has to be updated.

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

QRVizit — the product we are building: fixed code, page edited from a panel

Our own product, under development right now; we do not call it finished. The idea: the address a printed QR code points at is fixed once, while the page behind it stays editable from a panel. When a phone number or job title changes, the record in the panel is updated rather than the cards. Whoever scans downloads no app; the camera opens the page directly and Tailwind lays it out for a phone screen. Panel and visitor page live in one Laravel application, Inertia feeds the React interface, no separate API layer. Content is cached in Redis, records stay in MySQL. The boundary: no basket, no order record, no payment step.

Read the case study →

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

  • When a campaign ends, do the cards we put in the box become waste?

    Avoiding exactly that is why the idea is built this way. The printed code points at one address; when the offer changes, the page behind that address changes and the card stays as it is. The print decision is taken once, the content decision as often as needed.

  • Can we use QRVizit today?

    No, we are building it now. We do not present it as a finished product and we give no date. What we can share today is the idea itself: the split between a fixed address and a page that can change, and the decision to hold both in one application.

  • If one code is scanned many times over, does the page slow down?

    We make no speed claim we have not measured. What we can say sits in the design: page content is cached in Redis, so every scan of the same code does not reach MySQL.

  • Who edits the page, and does a second system need updating too?

    Editing stays in the panel, with the business itself. Because the panel and the visitor's page live in one application, changing content starts no second service that also needs updating, and we build no separate API layer.

E-Commerce in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Let's plan your catalogue and your checkout.

Get a quote or open the service