DemandStockIncoming
01 / Purchasing
Buy with the full picture.
See demand, stock, and incoming supply before committing to more.
Software & private AI for distributors
Your ERP data.Better daily decisions.
We build tailored software and private AI to help your team buy, price, manage stock, and prepare quotes.
Not ready to talk? Explore the free field guide. No email required.
Information → action
ERP recordsYour business rulesTeam review
Your existing ERPBuilt around your rulesYour team stays in control
Where we can help
Everyday decisions.
A clearer way forward.
Pick a problem. We shape the solution around your operation.
Cost (dashed)Sell price (solid)
02 / Pricing & margin
Spot prices worth reviewing.
Bring cost changes, discounts, and overrides into view.
Slow stockAnother branch
03 / Inventory
Give idle stock a next step.
Prioritize a transfer, return, discount, or write-down for review.
Concept illustrations. Each workflow is scoped to your business.
Prepare quotes.
Match items, check availability, review a draft.
Get useful answers.
Reports and questions, using your business definitions.
How it connects
Your information.
Your rules. Useful answers.
Private AI can help across approved information or within one agreed workflow.
01 / Connect
ERP + documents
Use the information your team approves.
02 / Tailor
Your business rules
Apply your definitions and permissions.
03 / Review
Answers + drafts
Check the sources. Your team decides.
Need local AI? We assess on-premises processing, infrastructure, and dependencies.
Start with the ERP you already use.
Environments to discuss
Eclipse · Prophet 21
NetSuite ERP
SAP ERP
CloudSuite Distribution · SX.e
ERPNext
Integration is scoped to your ERP, version, and available data access.
Product names and logos belong to their respective owners. Inclusion does not imply a partnership, endorsement, or certified integration.
Illustrative purchasing workflow
Before you buy more,
check what you already know.
The starting point
Your ERP + supplier records
-
01 / Stock
Available elsewhere?
Review a transfer
-
02 / Supply
Delivery overdue?
Check incoming supply
-
03 / Price
Buying cost unclear?
Confirm the price
Your buyer reviews the draft.
Your rules guide it. Your team decides.
Illustrative review brief / fictional example
What your buyer would review.
- Evidence
- Item and branch references, stock availability, open supplier orders, quoted cost, and when each source was last updated.
- Draft for review
- Consider a branch transfer before placing a new order. Flag an overdue delivery and any unconfirmed buying cost.
- Acceptance checks
- Compare source records with the ERP, apply agreed transfer and buying rules, flag missing information, and require buyer approval before any change.
This describes a sample output, not a customer project or a live product. The fields, rules, and review criteria are agreed for each engagement.
Discuss your review requirementsBuilt around your business
You set the boundaries.
Agree the environment, access, and terms before delivery.
Your environment.
Designed for on-premises deployment. Local AI and dependencies are assessed for your workload.
Your access rules.
Define permissions and support access. Keep consequential changes under review.
Your business data.
You own your data. dstl software is licensed; source-code ownership is not transferred.
Deployment and access follow agreed terms. More on control and licensing →
How we work
Start small.
Prove something useful.
One workflow, a clear scope, and a measure of success. Fees and timing agreed up front.
Map the problem.
Agree the priority, data, ERP access, and baseline.
Build & validate.
Test a focused solution with your team against agreed criteria.
Roll out & improve.
Agree deployment, training, and support. Expand where it helps.
What to bring to the first conversation.
Bring one recurring decision, the ERP product and version, who reviews it, and a description of the reports or records available. You do not need to send business data in the first email.
The conversation identifies the priority, constraints, and questions that need scoping. A proposed scope sets out the inputs, sample output, acceptance checks, deployment responsibilities, fees, and timing before paid work begins.
About dstl
The business problem comes first.
dstl builds solutions around your people, processes, and existing systems. We choose the approach that fits the problem—private AI is one option.
Tell us about your operationCommon questions
A few things to know.
Will we need to replace our ERP?
We start with your existing ERP. Integration and any required changes depend on its product, version, data access, and the workflow you choose.
Can the AI run on our infrastructure?
We assess local processing for your workload, including model capability, infrastructure, access, and operating responsibilities. Feasibility is confirmed during scoping.
Does it need an external AI service?
We assess a local model where external inference is unsuitable. Processing paths and external dependencies—including ERP, identity, and support services—are documented before commitment.
What do we own?
You own your business data and control agreed deployment and access. dstl software is licensed; software and source-code ownership are not transferred. Bespoke deliverable rights are agreed separately.
How are answers and recommendations checked?
We agree reference questions, sources, calculations, data freshness, and acceptance criteria. Missing information and decisions requiring human review are defined in scope.
Can it place orders or change prices?
Reading, drafting, and executing are scoped separately. ERP changes require supported integration, authorization, approval, and their own acceptance criteria.
What does an engagement cost?
Fees depend on workflow scope, ERP access, data preparation, deployment, and support. We agree fees and timing before any paid assessment or delivery. For example, a purchasing review may begin with stock, open orders, and supplier costs for one agreed workflow. Data access, preparation, and approval requirements determine the scope; a wider rollout is sized separately.
Let’s start with your operation
Bring us one workflow worth improving.
Tell us the decision, the systems involved, and what better would look like.
Email dstl info@dstlconsulting.com