Retail & homeware
The pain
Store stock does not agree with the e-shop, and you find out on the order you cannot fulfil.
What we do
One stock picture, synced in real time, with stores and the e-shop reading the same source.
ERP integrator
Most Soft1 partners install it. We extend it.
We are a SoftOne partner with our own development team — .NET, .NET Core, Entity Framework, React. When your process does not fit stock Soft1, you do not change your process.
What we implement
The whole Soft1 range, and everything hanging off it.
From first install to maintaining an environment that has been running for ten years.
SOFT1 ERP SERIES 6
Trading, accounting, warehouse, production. Installation, configuration and upgrades. [VERIFY naming]
SOFT1 CLOUD ERP
The same ERP on a cloud model, with infrastructure management staying with us.
SOFT1 CRM
Sales, opportunities and service, on the same customer data your finance team sees.
MYDATA & E-INVOICING
Transmission, classification, reconciliation and handling rejections — not just the initial switch-on.
PAYROLL & DIGITAL WORK CARD
Payroll, time tracking and the Digital Work Card, with submissions that land on time.
ENTERPRISE MOBILITY
Sales reps, warehouse staff and field engineers on the same data as head office.
The differentiator
"That is not possible" usually means "your partner does not do it".
Every Soft1 partner configures. Configuration ends where the standard product ends. Past that point, the usual answer is that you should change how you work.
We have gone past that point: custom screens, custom reports, custom pricing logic and APIs that do not ship in the box — for a publishing house, a winery, a coffee importer, a homeware retailer, a food distributor and a travel agency.
It also means that when legislation or your process changes, the change is days of work rather than a ticket in someone else’s queue.
How we work
Five phases, each with a stated duration.
Durations are indicative and are fixed during discovery. We do not start an ERP project without agreeing where it ends.
-
01
Discovery
2–4 weeks
We map processes, data and what costs you money today. Deliverable: scope, cost and timeline.
-
02
Design
2–3 weeks
Configuration, integration list and data migration plan, signed off before any code is written.
-
03
Build & integrate
6–12 weeks
Setup, custom development and integration with your other systems, in a test environment.
-
04
Migrate & train
2–4 weeks
Historical data migration, parallel running, and training by role rather than by screen.
-
05
Support
Ongoing
Helpdesk with committed response times, further development, and infrastructure monitoring.
Sectors
We start from the process that is costing you.
Every sector has one point where a stock ERP runs out. Usually it is the reason you are reading this.
Wine & beverage
The pain
Production tracked outside the ERP, in spreadsheets, so cost per bottle is an estimate.
What we do
A custom production tool wired into Soft1: stock, stages, participants and full reporting.
Publishing & media
The pain
Traffic peaks that take the infrastructure down exactly when it matters.
What we do
Clusters with load balancing, cache and CDN — and the ERP steady behind them.
Wholesale & distribution
The pain
Per-customer price lists and discount policy that end in manual invoice corrections.
What we do
Pricing rules inside the ERP, so the right price comes out on its own.
Food & delivery
The pain
Batches, expiry dates and traceability that an inspector asks for and nobody can find quickly.
What we do
Batch management from goods-in to dispatch, connected to the WMS.
Travel
The pain
Bookings in one system, receipts in another, reconciled by hand at month end.
What we do
Bookings wired into accounting and myDATA, so reconciliation becomes a check rather than a job.
ERP projects
What we have delivered.
NEF-NEF Homeware
NEF-NEF Homeware
- ERP
- Hosting
- IT Services
Braincandy
Braincandy
- Hosting
- IT Services
Semeli Estate
Semeli Estate
- ERP
FAQ
What people ask before they sign.
How long does a Soft1 implementation actually take?
Twelve to twenty-three weeks to go live, across the five phases above, then ongoing support. What moves a project within that range is the integrations and the quality of the data being migrated, not the user count. The range per phase is fixed during discovery, before build starts.
We already run Soft1 but our current partner is unresponsive. Will you take it on?
Yes, and it is one of our most common projects. We start by documenting what exists, what is documented, and what depends on one person. We will tell you exactly what we found, even when it is unwelcome.
What happens to our data if we decide to leave?
Your data is yours. We hand over database backups and documentation of any custom work. There are no clauses designed to make leaving difficult.
Can you connect the ERP to the e-shop we already have?
Usually yes. We have connected WooCommerce, Magento, Shopify and nopCommerce. If your platform is not on that list, what matters is whether it exposes an API — and we check that during discovery.
Who is accountable when the problem sits between two systems?
We are. That is precisely why we keep ERP, integrations, infrastructure and support under one contract.
Tell us what you are running today.
Which system, how many users, what hurts, and by when it has to be fixed. That is where a useful conversation starts.