VKraft Software Services

Loading

Stock you cannot see, you cannot sell.

ERP, warehouse systems, branches and partner channels each hold a piece of the availability picture, and most of them were last right overnight. We connect them so what the portal promises matches what the shelf holds.

SKAvailabilityONE SKU · ALL LOCATIONSSellable
On handERP
Reserved & pickingWMS
Branch stockBranches
On orderSupplier PO
One number

FOUR SYSTEMS · ONE NUMBER

Where it breaks

Everyone has an availability number. No two of them agree.

The ERP has one, the warehouse has another, the branch has a third and the portal is quoting last night's. The gap between them is what a customer experiences as a broken promise.

Availability is only true once a night

The portal quotes a figure the batch produced hours ago. A rep promises against it, the warehouse cannot fill it, and someone in customer service explains the difference.

What we do

Stock movements stream as they happen, so availability is a current figure rather than a nightly snapshot.

Every branch keeps its own version

Local adjustments, unrecorded transfers and a spreadsheet the branch manager trusts more than the system. Head office sees a total that nobody on the ground recognises.

What we do

One availability model with each location's contribution visible inside it, so you can trace a disagreement to the branch that caused it.

Pricing and rebates live outside the systems that use them

Contract prices, volume tiers and rebate agreements sit in spreadsheets. The portal quotes one number, the invoice carries another, and the rebate accrual is reconstructed at quarter end.

What we do

We hold pricing and rebate terms once and apply them everywhere, with the calculation attached to the line it produced.

How it works

Every system keeps its own stock. You get one number you can defend.

We normalise movements, reconcile availability across locations and allocate orders against it, and every figure keeps the parts it was made from.

SYSTEMS OF RECORDNORMALISE · RECONCILE · ALLOCATECONSUMERSERPStock · orders · pricingWMS & branchesPicks · transfers · countsSuppliersPOs · ASNs · lead timesSales channelsPortal · marketplace · EDIEDI 850/855/856 · GS1 · APINormaliseCanonical product · order · stockReconcile availabilityOn hand · reserved · on orderAllocate & priceSourcing rules · tiers · rebatesPublish & evidenceAPIs · calculation trail · lot traceabilityREST · EVENTS · EDIB2B portal & salesAvailability · quotes · ordersMetricMonitorFill rate · feed healthEasy-InvoisInvoicing · rebate settlementRetailers & marketplacesFeeds · orders · confirmations

Scroll the diagram sideways →

Built on published standards

EDI 850, 855, 856 and 810 where your partners trade that way, GS1 identifiers so a product means the same thing to everyone, and REST and events for everything new.

Your cloud, or at the branch

The runtime sits on your cloud tenancy, in your data centre, or locally at branches with unreliable connectivity, so counts and picks queue until the link returns.

Monitored after go-live

Feed health, availability drift between systems and unmatched product codes all land on one dashboard, so the number stops being a surprise at month end.

Products

Products that arrive already connected

Easy-Invois and MetricMonitor read the same product, order and stock model, so what is invoiced matches what was promised and what was shipped.

Wholesale billing
E-invoicing

Easy-Invois

High-volume B2B invoicing across retailers, dealers and wholesale partners, with tiered pricing, rebate settlement and multi-country tax rules wired into the ERP you already run.

Explore Easy-Invois →
Observability

MetricMonitor

Fill rate, inventory turns, order-to-cash throughput, partner feed status and integration health on one screen, with alerts before a stockout becomes a phone call.

Explore MetricMonitor →

How we work

We do not publish a number you cannot explain.

Every availability figure carries the parts it was made from and the time each part was last confirmed. When sales and the warehouse disagree, the answer is in the record rather than in the argument.

Parallel running is the default

It is included in every engagement. A new feed runs beside the existing one until the counts agree.

Every figure shows its components

On hand, reserved, in transit and on order, each with the location and the timestamp behind it. You can open any total and see what built it.

Going back is a configuration change

Whatever we replaced stays configured until you retire it. Reverting during a peak week means flipping a switch. There is nothing to restore.

Recent work

One SKU, several branches, three different answers

Anonymised at the client's request

A wholesale distributor ran an ERP at head office, a warehouse system at the main depot, and branches that reconciled by spreadsheet. The B2B portal quoted whichever figure the overnight job had produced, and the sales team had learned not to trust it.

We built one availability model that keeps each location's contribution visible, streamed stock movements as they happened, and moved contract pricing out of spreadsheets into the same path as the order.

Talk to us about your estate →
Before
  • Availability refreshed overnight
  • Each branch trusted its own count
  • Contract pricing held in spreadsheets
  • Rebates reconstructed at quarter end
After
  • Movements streamed as they happen
  • One number, with its parts visible
  • Pricing applied from one source
  • Rebate accruals traceable to the line

Questions

Answers before you ask

Through API-led middleware, usually webMethods or Apache Camel depending on what you already run. Each system maps into one canonical product, order and stock model rather than into each other, so the number of systems you operate stops driving the number of interfaces you maintain.

Get started

Book an assessment

Tell us where your availability number comes from and where it stops being true. An integration architect reviews it and comes back within two working days.

  • A read of your ERP, warehouse, branch and channel estate
  • Where availability drifts, and by how much
  • A sequenced plan with effort ranges, written for your engineers

Loading security check…

Your details stay with VKraft and are used only to answer this enquiry.