Wegiel.io / Ways of working

Customer collection, delivery and several warehouses

Fuel yards need a clear handover from a customer agreement to stock preparation, documentation and payment checks. These examples describe work to examine with the team; they are not completed customer projects.

Choose your business profile

See how your business works.

Follow a day-to-day task through the team's work, the system's actions and the outcome. The examples below show different business models.

From the first action to settlement

From customer agreement to payment

Product and quantity pass from sales to the warehouse, documents to the customer and the receivable to the office.

Legend
  • Action
  • System automation
  • Outcome
  • Handoff: the same number on the arrow and under the step
  1. Agreements
  2. Stock
  3. Collection or delivery
  4. Settlement
    • Office

      Outcome Document and receivable

      The office checks due dates, payments and the remaining amount.

Example workflow

Retail yard: from choosing fuel to collection

A customer buys fuel for collection. Sales agrees the product, quantity and price; warehouse staff check what can be prepared.

Fuel-yard sales workflow

Sales agrees the purchase, warehouse staff confirm quantity, and documentation and payment complete the workflow.

Legend
  • Action
  • Decision
  • System automation
  • Outcome
  • Handoff: the same number on the arrow and under the step
  1. Purchase
  2. Preparation
  3. Collection
  4. Documents and payment

What the system does

  • Quantity checks when reserving stock

    The system calculates free stock as the physical balance less active reservations and blocks reservations above that amount.

  • Parameters on the quality document

    Product data and entered parameters are used to prepare the certificate printout or PDF. The responsible person checks completeness.

What the team gains

In this example, the customer receives the agreed goods and documents. Warehouse staff record issue; sales and the office know how settlement is handled.

Product catalogue after searching for DEMO-WEG: two fuels measured in kilograms and a separate service. Sample records.

Optional receipt sales work with Novitus devices with NoviAPI and with Posnet Online through separate local applications; we activate the Posnet integration, prepared according to the API documentation, with the first device. We select the device, workstation and settings; KP/KW cash documents form a separate flow.

Example workflow

Distributor: delivery with a clear handover to finance

A customer orders fuel for delivery. Sales agrees terms, address and date; warehouse and transport staff receive the details needed to fulfil it.

Fuel delivery and customer settlement

Sales passes terms to warehouse and transport staff; the office takes over documents and the receivable.

Legend
  • Action
  • Decision
  • System automation
  • Outcome
  • Handoff: the same number on the arrow and under the step
  1. Order
  2. Preparation
  3. Delivery
  4. Settlement

What the system does

  • Match a payment to its document

    After statement import, the system proposes links between transactions and documents. Unambiguous matches can be settled automatically under enabled rules.

  • A task for the account manager

    Enabled CRM rules can create a task when an order or delivery is overdue. The account manager agrees the next step with the customer.

What the team gains

Customer terms, fuel preparation, quality documentation and the receivable are available to the appropriate people in one system.

Demonstration certificate editing form: selected product and fuel quality parameter table. Sample data. Complete and verify parameters against fuel documentation. The original screen is Polish and does not prove a localised ERP. The demonstration form is not evidence that a certificate has been issued or verified.

Transport and CRM automation follow the agreed scope. Before calculated excise can be used, the known product-setting gap must be repaired, then applicable fuel parameters, periods and resulting documents verified and accepted.

Example workflow

Several warehouses: choose a location before promising supply

Sales chooses the fuel and unit from shared records. Existing reservations at the proposed warehouse require a decision: prepare the goods there or offer another warehouse or date.

Stock distributed across warehouses

Choose the location using checked quantity, active reservations and warehouse/sales decisions.

Legend
  • Action
  • Decision
  • System automation
  • Outcome
  • Handoff: the same number on the arrow and under the step
  1. Customer requirement
  2. Location check
  3. Fulfilment choice
  4. Handover for goods issue
    • Salesperson

      Outcome Confirm the collection location

      Sales agrees terms with the customer; warehouse staff take over separate goods-issue work.

What the system does

  • Free stock calculated separately per warehouse

    The system accounts for active reservations for the product in the chosen warehouse. Staff see locations permitted by their access rights.

  • Reservation-release record

    When an authorised person releases an unused reservation, the system records who acted and when.

What the team gains

Warehouse staff confirm the quantity to prepare; sales gives the customer terms based on a checked fulfilment location.

Product catalogue after searching for DEMO-WEG: two fuels measured in kilograms and a separate service. Sample records.

Product records identify fuel and units before the warehouse check. A reservation plans a quantity internally. Authorised staff handle the sale, goods issue and any warehouse transfer separately.

Connected areas of work

The process draws on the whole business.

Select features to suit the team's tasks, and check the package scope and extensions in the offer.

Sales and customers

Customer terms before the next order

Contacts, account managers, offers, price lists and conversation history retain customer terms. Tasks, complaints and receivable checks continue the relationship after sale.

Customers, documents and settlements Fuel sales and documents

Stock and goods issue

Quantity prepared at the right warehouse

Stock, active reservations and movement documents organise yard work. Sales passes the agreed product and quantity; warehouse staff handle issue.

Reserve quantities before goods issue Fuel sales and documents

Quality and records

Fuel parameters with documents for handover

Certificates link fuel to parameters, units and sources. Excise declarations, registers and printouts support record-keeping; calculated excise still requires repair of the known gap and verification and acceptance of parameters, periods and documents before use.

Quality certificates and documentation Fuel sales and documents

Settlements

Document, due date and payments in context

The office checks FSW invoices, FSWK corrections and receivables. Statement import and transaction matching support settlement; KP/KW and fiscalisation have separate purposes.

Fuel sales and documents Customers, documents and settlements

A scope tailored to your business activities

Use your business process to guide your system choice.

The system is available as SaaS. During the presentation, we will discuss the team's tasks, roles, required integrations and starting data. The offer explains how to select a package, extensions and setup scope.

Screenshot preview

Screenshots have been omitted from the printout.

Your privacy

This website does not run optional analytics or advertising. Below we describe the data stored in your browser and the preferences you choose.

  • Browsing public pages does not create session or CSRF protection cookies.
  • We remember your chosen theme for the current session in this browser tab.

We use the information you share when contacting us to respond to your enquiry.

We will remember that you closed this window for the current browser session. This is a display preference. Closing the window does not mean consent to marketing or tracking.

Privacy settings

These settings apply to wegiel.io in this browser. They are not transferred to the customer portal or other domains.

Website operation and your preferences

  • Browsing public pages does not create session or CSRF protection cookies.
  • The light or dark theme you select with the button is remembered for the current session in this browser tab.
  • Closing the privacy notice is remembered for the current browser session. This is a display preference, not consent to tracking.

We use the information you share when contacting us to respond to your enquiry.

We currently use no optional analytics, advertising or embedded services that require your consent. You do not need to accept anything to use the website.