Add-on development
Native B1 add-ons and external web applications built on the Service Layer — packaged, versioned and licensed so the same product can be deployed to the next customer without a rewrite.
SAP Business One · WMS · Development & consultancy
Standard B1 gets you most of the way. CSC-WORK builds the rest — add-ons, integrations and extensions for SAP Business One and the systems around it, from a single stubborn report to a full warehouse or transport system.
Track record
More than a hundred SAP Business One projects delivered across Latin America, Central America, North America, Europe and Asia — different languages, tax regimes and warehouse realities, the same product underneath.
What we do
Most engagements start the same way: something in B1 does not fit how the business really operates, and nobody wants to change the business. We close that gap in code, and we hand back something you can maintain.
Native B1 add-ons and external web applications built on the Service Layer — packaged, versioned and licensed so the same product can be deployed to the next customer without a rewrite.
Implementation, extension and troubleshooting of WMS on top of B1 — bin logic, directed put-away, licence-plate handling, pack-out and label design, including the flows a standard warehouse module does not cover.
Carriers and shipping, e-commerce, EDI, CRM and finance systems wired into B1 — with reconciliation, retries and error handling designed for real traffic rather than a clean demo dataset.
Crystal reports, B1 queries and purpose-built dashboards for the point where the standard reports stop answering the question the business is actually asking.
Recovering, documenting and re-platforming add-ons whose source code, original vendor or original author has gone missing — so an upgrade stops being the thing that can never be scheduled.
Ongoing development capacity, upgrade support and monitoring — from someone who already knows your database, your customisations, and why that one posting routine is the way it is.
Sectors & systems
Very few businesses run on SAP Business One alone. Most of our work lives at the seams — where the till, the storefront, the hire desk or the trading partner has to agree with the ledger, every day, without anyone rekeying it.
Multi-store and multi-currency retail tills reconciled to B1 — daily takings, payment tender breakdown, stock movements and returns posted without a spreadsheet in the middle.
Hospitality and facilities systems joined to the ledger: folios, room and service revenue, night audit, deposits and city ledger arriving in B1 as clean, auditable postings.
Contracts, availability calendars, on-hire and off-hire, damage and consumables billing, and the asset depreciation that has to keep agreeing with finance while the kit is out on site.
Tiered pricing, rebates and vendor programmes, multi-warehouse replenishment, landed cost and margin visibility per customer, per line — the numbers a distributor actually gets judged on.
Storefronts kept honest against the ERP: catalogue and pricing out, orders and payments in, live stock availability, and fulfilment status pushed back to the customer without a nightly-batch excuse.
Purchase orders, acknowledgements, advance ship notices and invoices mapped to your partners' spec, with acknowledgement tracking and exception handling — because the chargeback lands on you, not on the VAN.
Process improvement
Software is the last step, not the first. We baseline the flow as it actually runs today — order to cash, procure to pay, receipt to put-away — count the touches, the waiting and the rework, and only then decide what to configure, what to automate and what to leave alone. Every engagement gets a number to beat and a way to prove it.
Order-to-cash improvement profile — the shape of change we design an engagement to deliver.
These are the improvement targets we design an engagement around, not a claim about your business. Step one is always baselining your real numbers — and we re-measure them the same way after go-live, so the result is arguable in a board pack rather than in a testimonial.
Our products
Consultancy work that kept repeating became product. Each of these runs on the same foundation — shared licensing, the same SAP Business One Service Layer client, the same design system — so they install alongside each other and share data instead of fighting over it.
Accounts receivable collections
Turns the aging report into a working queue. Collector worklists, promises to pay, dispute tracking, dunning and cash-forecast visibility — driven directly from B1 invoices and incoming payments.
Own-fleet transport management
Route planning for companies that run their own trucks. Plans against real constraints — weight, volume, pallet positions, delivery windows, driver hours — then writes the result back as deliveries with route costs allocated in B1.
Warehouse management
A mobile-first WMS for B1 sites that need real warehouse discipline: directed receiving and put-away, bin and licence-plate control, pack-out with SSCC labels, cycle counting, and stock accuracy you can defend at audit.
Stage labels above are kept current on purpose — see how we talk about what is finished.
Client access
Every hosted CSC-WORK platform sits behind authentication — support included. If you are a current customer, your credentials were issued during onboarding. Access is per-user, so activity is attributable, and seats can be added or revoked by your administrator.
Cannot get in, or not sure which platform you are on? Email us and we will sort it out — we do not reset anything over chat.
How we work
ERP projects fail slowly and expensively. Ours are structured so that if the project stopped tomorrow, the part already delivered still works and still earns its keep.
If something is modelled, estimated, or not yet posting to SAP, the screen says so — in the demo and in production. You should never have to find out at go-live that a number was decoration.
We start in the warehouse, on the phone with a collector, or in the dispatch office — not in a requirements template.
Each slice is a working end-to-end path, deployed and usable, rather than a layer that only makes sense once everything else lands.
Migrations are additive and reversible. A schema change ships with a backfill — never a wipe-and-reseed of a live system.
Documented, monitored and deployable by someone other than the person who wrote it. Then we stay available for the next change.
The technical foundation
B1 add-ons have a reputation for being fragile, unversioned and impossible to move. Ours are containerised applications with proper release engineering behind them.
Service Layer and DI API clients generated from B1 metadata, working identically against SQL Server and HANA.
Python and FastAPI services with a shared React front-end design system, so every product looks and behaves like one suite.
Signed, node-locked licences with online and air-gapped activation, seat control and per-feature entitlements.
Kubernetes deployment, metrics, log aggregation and alerting from day one — on your infrastructure or ours.
Start a conversation
The first conversation is a working one, not a sales call. Bring the process that does not fit, the report nobody trusts, or the add-on nobody can maintain — and we will tell you honestly whether it is a configuration problem, a development problem, or something you should not spend money on at all.