Connecting inventory software to an online store
Decisions about product identity, available stock, update timing and failed requests before building an integration.
Services
Custom software
We develop applications for specific business tasks: collecting requests, managing records, reviewing approvals and giving customers access to their information.
When this service helps
The requirements begin with a task your staff or customers need to complete. We map its steps, records and access rules before deciding which screens and features belong in the application.
Staff copy the same records between spreadsheets, email and separate tools.
Your work needs shared status tracking, customer access or permissions your current tools cannot represent.
What you receive
Workflow and first-release brief
The required records, fields, status changes and acceptance checks for completing the main task.
Application and administration screens
Forms, searchable lists, review screens and exports organised around repeated tasks, including invalid or incomplete inputs.
Data model and permission matrix
Record relationships and an explicit list of what each role may view, change, approve and export. Existing data can be mapped for import.
Operating instructions and deployment
Checks of the main workflow and restricted actions, deployment configuration, and instructions covering recurring operating tasks.
Example workflow
From an incoming request to an approved record
One example of a workflow an internal application can support. The records and roles follow the actual task.
Submit
Collect the required information and validate the fields.
Review
Give the responsible role a queue and the relevant records.
Approve or return
Record the decision, status and permitted changes.
Notify and export
Share the result and produce the required output.
Questions about this service
What belongs in the first release?
The main workflow and the roles, screens and data needed to complete it. Additional features are listed separately so the first release remains usable and testable.
Can existing spreadsheets or application data be imported?
We inspect a sample export or documented API and check identifiers, required fields, duplicates and relationships. That determines the cleanup and import work.
How are different access levels checked?
The permission matrix names the records and actions available to each role. Testing covers allowed actions and attempts to access or change data that role should not control.
Related reading
Practical notes on the decisions behind this work.
Taking over an existing website
A handover checklist for ownership, access, backups, custom code and the first maintenance priorities.
What needs to change?
Share the current website or tools, what needs to work differently and any deadline you already have.