16
modules in production
50+
screens, Turkish UI
90+
database tables
17+
active users
Work behind this service

One ERP, in production

Designed, built and maintained by one developer from May 2025 to August 2026, then handed over to the client in September 2026.

Client · ManufacturingIn production · handed over Sep 2026

SPSTARPLAST Manufacturing ERP

A production ERP for an insulation anchor manufacturer: 16 modules and 50+ screens in Turkish, covering sales, production, the mold shop, quality, purchasing, shipping and inventory.

  • Integrated with the company's LOGO ERP: accepted quotes post to LOGO as sales orders
  • Next.js 15, React 19, TypeScript and Supabase PostgreSQL
  • Built and maintained May 2025 – Aug 2026, then moved to the client's own accounts with no downtime
What you can hire for

What a custom ERP can cover

These are the modules SPSTARPLAST runs today. A new ERP starts from your own process, not from this list.

Sales and quotes

Customer price lists, multi-currency quotes at live exchange rates, cascaded discounts and PDF export. Accepted quotes post to LOGO as sales orders.

Production planning

Daily plans per machine and shift, work orders with live status, and unfinished jobs that roll over to the next day.

Mold shop

A registry of injection molds with cavity counts, shot counters, maintenance thresholds and open issues per mold.

Quality

Incoming, in-process and final inspection forms, quality tests and an ISO document library.

Purchasing, shipping and stock

Purchase orders, carriers and shipping plans, inventory and stock counts in the same system.

Access and audit trail

Each user is granted any of 14 functional areas. A company-wide activity feed records who changed what and when.

Process

How an ERP project runs

  1. Start from the systems you have

    SPSTARPLAST already ran LOGO ERP, so the new system syncs with it instead of replacing it.

  2. Rules in the database

    Document numbers, order totals, mold shot counts and plan rollover run as PostgreSQL functions and triggers, so every screen sees the same numbers.

  3. Your team's language

    The SPSTARPLAST interface is in Turkish, the language its users work in; the technical documentation is in English for whoever maintains it next.

  4. Handover

    You get the repository, technical documentation and a technical-debt report, and the system moves to your own accounts. The SPSTARPLAST move had no downtime.

Questions

Frequently asked questions

Custom ERP or an off-the-shelf package?

Off-the-shelf is cheaper when your process matches the package. Custom pays off when the shop floor has its own logic, like mold shot counters or unfinished jobs that roll over to the next day. The build or buy ERP article walks through the costs.

Can it work with LOGO or our current accounting system?

The SPSTARPLAST ERP does: customer, supplier and stock cards sync in from LOGO, statements and purchase history come from LOGO, and accepted quotes post to LOGO as sales orders automatically. Other systems can be connected the same way when they offer an API or data to read.

Who owns the system at the end?

You do. At handover the code, database and hosting move to your own GitHub, Supabase and Vercel accounts, along with the documentation.

How long does an ERP take?

It depends on how many departments it covers. The SPSTARPLAST ERP was designed, built and maintained from May 2025 to August 2026, then handed over in September 2026.

Is the interface in Turkish or English?

The SPSTARPLAST ERP runs in Turkish, with English technical documentation for the code. A new system is built in the language your team works in.

Running the plant on spreadsheets?

Send a short description of your departments and the systems you use today. Savas will tell you plainly whether a custom ERP makes sense.

Or call (786) 788-1030

Savas Tutumlu

Who builds it

Savas Tutumlu

Founder & CEO, Stratagem Systems

Started the studio in Houston, TX in 2023 and now works from Istanbul. 30 projects shipped since.