Multi-tenant software

The result is not a demo, but a live production environment. When a new tenant is added, the boundary is copied; when a new rule is added, the neighbouring account does not generate a separate instance. The software is kept simple and rigid enough to handle the growing workload.

During the exploration phase, the question ‘which diagram do you want?’ is left until the end. First, the events are discussed: a tenant was opened, a row was locked, a report was filtered, an error remained in the draft. If these events do not share the same identity, there is no system, even if the number of entities increases. Shopsoft draws this tenant map using your documents; it does not impose a hypothetical process.

This is where the off-the-shelf package falls short. The package assumes the average tenant of an average company. If your account is exceptional, your rules are multiple, and your documentation is threshold-based, the package will either link every line to a person or filter nothing at all. A custom limit incorporates the exception into the rule; it does not leave the exception in the notes section.

Shopsoft’s discovery process isn’t wrapped up in three unsubstantiated statements. ‘We have plenty of customers’ isn’t enough. An unaccounted tenant, a leaked report or an inconsistent document will come to light. These documents reveal which rule is missing. A schema cannot be selected without a rule being written. The software does not hide your exception as if it were a source of shame; it records it.

Going live does not necessarily mean that all tenants have to go live on the same day. The first phase resolves the tenant-lock-leak triad. The sharing mechanism only makes sense if this triad is sound. Otherwise, it keeps Excel alive behind the nice-looking diagram. Shopsoft does not make this sequence a matter for negotiation; it is a condition of the agreement.

In exploration, the phrase ‘share first, set boundaries later’ often amounts to postponing the core issue. Blind sharing does not unify the record; it gives rise to a second instance. Shopsoft keeps the initial allocation narrow but does not leave it unregistered. A narrow allocation masks the tenant’s identity. An unmasked identity seeps into the neighbour’s account the following month.

Custom software development is the owner of the spine. This page does not take it over; it describes the tenant’s boundary. Scalable software architecture carries the volume; the volume is not generated by the tenant. SSO and identity management deepens the entry; the entry is not a line lock.

A boundary is not established simply by ‘adding a customer code’. A code can act as a filter; it is not an identifier. Shopsoft distinguishes, during the discovery phase, where the code is located and where the line is locked. If there is no lock, the code conceals the leak.

Shopsoft re-runs this morning’s exploration using your data. Which steps are carried out in Excel, which in email, and which with a ‘I know’ response? The software works with you to map out which of those steps to record.

A reverse transaction may occur in the second half of the same day. If there is no record, the rejected line becomes a new document; the tenant and the document do not match. If there is a limit, the reversal is linked to the original line. This is not the ‘problem-solving’ promise of multi-tenant software; it is a natural consequence of tenant identity.

On peak days or during campaigns, the number of tenants surges. The system operates based on rules, not by locking limits. Users cannot write a panic exception; the threshold remains in the draft. The manager sees the risk of that day whilst the transaction is on hold, not in the following week’s report. Growth does not spawn a new Excel spreadsheet; it adds a rule.

The same backbone provides a replicable boundary for the opening of a new tenant. A new account replicates the schema; it does not replicate the business identity. The new rule is versioned; the field does not ‘remember’ the old path. This is the promise of growth in multi-tenant software: adding rules, not rewriting. The package addresses this growth by adding schemas; it addresses it by adding boundary records.

A night-time outage usually amounts to ‘we’ll look into it tomorrow’ at most companies. If there’s a limit, half the issue remains in the draft; the neighbouring record doesn’t appear in the morning. Backup and disaster recovery This deepens the issue; this page doesn’t resolve it. The condition is simple: an outage does not generate a second tenant.

It will become clear during the scoping phase which system is to be connected. A fixed list of technologies is not published. The architecture is kept flexible enough to protect your existing investment, yet strict enough not to disrupt operations.

Successful integration does not simply mean ‘connected’. Blind copying produces a second reality. Shopsoft distinguishes, during discovery, which events are real-time, which are queued, and which require human verification.

If the order, rule or external channel does not match the line, the field is still closed by telephone. These elements are explored in greater detail on separate pages; the rule here is that multi-tenant software does not ignore them, but links them to the tenant’s language. If the link is broken, the boundary claim remains valid.

SSO and identity management carries the entry. The entry is not a row lock. Multilingual software binds the language layer. The language does not generate a tenant. Scalable software architecture carries the volume; the volume is not a boundary.

Data security contains the section that the report can navigate through. The section does not generate any text. This page does not display that section; it shows where the boundary lies.

Development is divided into approved architectural segments. The first segment is usually the ‘tenant + lock + leak’ trio. The concept of sharing only makes sense if this trio is sound.

The data model is locked before the schema. The business entity, tenant ID, lock, association event and authorisation slice are distinct concepts. Merging these into a single ‘customer code’ may be quick in the short term, but is fragile in the long term. Shopsoft does not promise a table name; it requires these distinctions to be maintained.

The test simulates errors rather than a smooth run: the same order appearing for two tenants, threshold exceeded, partial closure, identity change, report omission. If these scenarios fail, the live environment becomes a second Excel spreadsheet. Performance metrics cannot be made up; filtering and sorting are discussed based on your tenant volume.

A boundary that has been brought into production does not close simply because ‘the schema is complete’. A new tenant type, a new rule and a new account all require the same identity. Shopsoft designs this requirement not as a rewrite but as the addition of a rule. If a rule cannot be added, it means the architecture was designed too narrowly from the outset; this narrowness becomes apparent during the discovery phase.

The report layer sits above the boundary; it does not replace it. The admin dashboard does not correct the deviant record. First, the job line, tenant version and link event are generated correctly; then the cross-section is read. The reverse scenario reveals three truths behind the attractive graph. This distinction sets multi-tenant software apart from flashy dashboard packages.

This framework is intended for companies where tenant records are closed in Excel or via email, and where exceptions to the package are noted. Small operations that run on a single account, a single set of rules and a single report often do not require this level of detail. If your requirement is not record deduplication but rather the elegance of the schema, then this page is not the right place for you.

During the Shopsoft discovery phase, we ask about your approval process, the number of tenants and the current status of the project. The software is not sold until the answer is clear. We do not impose a ready-made package. The decision hinges on whether the tenant-key-leak trio sees the same reality. Requesting a meeting does not constitute a binding offer; the architecture is discussed once the documents are on the table.

The reader should take three things away from this text. Multi-tenant software is not a filter. An off-the-shelf package leaves your tenant in the lurch. Shopsoft defines the boundaries with your documentation; it does not publish package names or prices. The discovery process begins with a response within 24 hours. The first phase involves the tenant, the lock and the leak. The schema polish comes afterwards.

The final decision criterion is simple. If the same order spans three accounts, there is no limit. If a person can circumvent the current rule, the system is ineffective. If the newly created record does not lock the neighbouring one, the other party is lying. If the code has to be rewritten when a new tenant is added, there is no scalability. If you cannot answer ‘no’ to these four questions, the meeting should begin with a document, not a presentation. Shopsoft requires that document; it does not sell packages.

The team, which has been developing software in Istanbul since 2004, brings over 700 agencies’ worth of infrastructure experience to this project. No code is written until the ISO number is approved. Client logos may be withheld; confidential architecture is not disclosed. No competitor names are mentioned. The CTA is ‘Request a Meeting’. There are no demos, pricing or package options. We aim to respond within an average of 24 hours during working hours. The initial discussion does not constitute a binding offer.

The need for software often arises from the phrase ‘let’s segment our customers’. This phrase may not be the right starting point. The real requirement is for the row to be generated with tenant identification, for the filter to apply, and for the report to refer to the same record. The schema could represent these three elements. The document arrives, the tenant map is generated, the first segment is locked, and then the schema is opened.