Brands, stores and employees. Different roles within one service.

A brand needs different capabilities from a team manager. Internal operations must be able to administer the service. The employee app needs to support people on the shop floor.

We built separate web environments for brands, internal operations and team management. Backend services connect those environments with the employee app. Roles, organisations and activities establish the context for information and actions.

Activities include videos, questionnaires and individual or team-based actions. Preparing and publishing an activity, participating and receiving a reward are distinct steps. We represented those distinctions in the product’s business logic.

A transaction from another system does not automatically make sense inside the platform. Which store, brand, product and employee does it belong to? External systems describe those relationships differently.

We built import and conversion jobs to normalise the data into a shared model. Pub/Sub distributes processing across background tasks. The applications can work with their own data foundation and its defined relationships.

Financial processing also has a deliberate structure: payout batches, recipients and processing statuses connected to a payment provider. A request and its outcome are different records that the platform needs to keep connected.

IndustrylinQ built the cloud infrastructure and web applications. A separate team built the native iOS employee app under our guidance.

That division requires more than providing endpoints. App and web environments need a shared understanding of accounts, activities and progress. We coordinated our development with the work of the mobile team.

Each participant had an appropriate way into the same service. Brands could organise activities, managers could work with their teams, and internal operations could administer the product. Point-of-sale and payment providers became part of that service, with processing and business logic around them.

Businesses working with dealers or distribution partners face a similar question: what should each participant be able to do independently, and which information and agreements must stay consistent?

Explore our cloud architecture and integration approach or our role in platform development.