Skip to main content
GullySystem
East Asia · Software for businesses in Japan

Job, quality and invoice software for Japanese makers, integrators and inns, written to suit careful Japanese routines.

Japan’s small and mid-size firms cut metal, assemble electronics, integrate robots and run inns, and most keep exact records for tiered buyers. GullySystem is a Bengaluru company that writes software for those routines and supports it remotely. Nobody of ours lives in Japan, and we claim no customers there.

At a glance

Working with a team in India from Japan.

Japanese industry sits in supplier tiers, where a small shop turns a part for a mid-size firm that sells to a large maker, and each step is inspected and logged. Records must be tidy. A missing figure is noticed quickly.

Our team sits in Nagarbhavi, Bengaluru. Japan holds no office, staff or licence of ours, and we name no Japanese customers or partners because there are none yet. Sessions run through video, email and chat, and we say this before a contract is drafted.

How the work runs

What changes when your business is in Japan.

Hours, money, language and data are decided with you at the start, not discovered later.

Hours and calls

Tokyo clocks run 210 minutes ahead of India all year, with no clock change, so your morning meets our late morning and afternoon calls suit both sides. Urgent fixes still land the same day. Few meetings run late.

Language and documents

Screens and printed forms can be set in Japanese, English or both, and names, addresses and furigana must display correctly, so we test them before anything else. A Japanese reader on your side should approve every label and form before use, because tone matters. We are not native readers.

Consumption tax and invoices

Documents can carry consumption tax lines and a registration number field for the qualified invoice system. Rules and transition steps have shifted over time. Treat our settings as a draft and have your tax accountant, the zeirishi, confirm them before you issue anything.

Stamps, paper and approvals

Traditional offices still use seals, ringi routing sheets and the occasional fax, and software can mirror that chain by name and rank, with a record of who agreed. Stamps can sit beside it. Whether a digital approval satisfies a given customer is a point to settle with them.

Data and contracts

Personal data falls under the Act on the Protection of Personal Information. Large buyers may also ask where records are stored and who can open them. We answer in writing, in plain terms, and wording that carries legal weight is reviewed by your own counsel.

Where the first form starts

We begin with a walk through your floor or front desk. Each form is noted, with who fills it and who checks it. Then comes one form. We rebuild the form that causes the longest wait, and show the draft to the person who signs it before anyone else sees it.

Business in Japan

What the software has to fit.

The filing cycles, payment habits and licences a small business there already works around.

Precision parts and supplier tiers

Machine shops, press shops and mould makers quote against drawings and deliver to a large customer’s schedule, and drawing revisions land mid-job. A job record should hold the drawing revision, the lot, the inspection result and the delivery slip together, so a question months later has an answer. Nothing is guessed.

Robots, vision and automation

Integrators build cells that combine robots, cameras and sensors for factories at home and abroad, and each project carries a long bill of materials, commissioning visits and warranty calls over years. Margins hide in those details. Tracking each cell from quote to handover keeps them visible.

Electronics and component makers

Board assemblers and sensor makers buy parts in small lots and trace them by batch. A defect found at a customer must lead back to the reel and the date. Serial and batch records make that trip short.

Inns, hotels and local tourism

Ryokan, small hotels and guesthouses handle rooms, meal plans, seasonal peaks and guests from abroad. Bookings arrive from several channels at once. Holiday weeks such as Golden Week and Obon bring crowds that spreadsheets rarely survive.

Labour shortage and ageing staff

Hiring is hard, and skilled people are close to retirement, so know-how held in one head becomes a real risk. Writing routines into software, with checklists and records, keeps work moving when a veteran steps back. Handover gets easier. New staff learn faster.

Bearings, auto parts and lot records

Bearings and auto parts leave the plant in boxes of identical pieces. A claim names a lot and a line. Records must reach back. If a lot is recalled, the maker needs to list every box, every pallet and every customer shipment that carried it, from heat treatment through to the delivery slip.

Vision systems and sensor builds

Vision firms sell cameras, lenses, lighting and software as one package. Each unit leaves with a calibration record. A sensor maker adds the firmware version and the test result to every serial number, so a service call years later starts from the unit’s own history. Firmware changes between batches.

Ryokan meals and allergy notes

A ryokan serves set dinners, so the kitchen needs the headcount early. Allergy notes ride with the booking. When a guest changes the dinner time or adds a child’s meal, the front desk edits the booking once and the kitchen sheet updates itself for the cook.

Cities

Cities we write software for in Japan.

Make an informed decision

Make the scope specific to your business.

Work through a real example from your operation and agree the handoffs, controls and support the project needs.

Consumption tax and invoices

Can you explain the balance from its original documents?

Select a partly settled example in “Consumption tax and invoices”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.

Background reading: ERPNext: outstanding invoices

Stamps, paper and approvals

What needs fresh approval after a record is changed?

For “Stamps, paper and approvals”, change a material detail after approval during a scoped walkthrough. Agree the next responsible person and the evidence needed before the work can continue.

Background reading: ERPNext: approval transitions

Common questions

Questions from businesses in Japan.

Do you have staff or an office in Japan?

No. Our people sit in Bengaluru, and we say so at the first conversation. Japanese firms are helped from a distance, and if you need someone on site we will tell you before anything is signed.

Can the software work in Japanese?

Yes. Labels, forms and customer documents can be set in Japanese, English or both. Because we are not native readers, we ask a Japanese colleague of yours to approve the final wording.

Can it handle the qualified invoice system?

It can hold a registration number and print the lines such invoices need. The rules have changed in the past and may again, so your zeirishi should confirm the setup before you rely on it.

How do we cope with the time difference?

It is small. Japan sits 210 minutes ahead of India, so most of a working day overlaps. Standing calls fit a Japanese morning and an Indian late morning without strain.

Will our drawings and records stay private?

Access can be limited by role, and every view or change is logged. Tell us early where data must be stored. We answer such questions in writing, and your counsel should review the contract wording.

Can you replace our spreadsheets and paper forms?

Yes, in steps. We start with one flow, such as inspection sheets or delivery slips, and move the old data across. Paper and seals can run alongside until your team is comfortable.

Can a part be traced from raw material to delivery?

Yes. Every lot carries its material certificate, machine, inspector and delivery slip, so a customer’s auditor can follow one part from bar stock to the loading dock. We settle the fields with your quality manager before the first lot is entered.

From Japan

Tell us what you run.

Share your requirements and an engineer will read them before getting in touch, at an hour that suits your day.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements