VulCode

enova365 integration with your store, BaseLinker and KSeF

enova365 has built-in KSeF support and ready connections to popular platforms. We write an integration where your sales, panel or company system go beyond what enova365 connects by itself.

Invoicing and ERP
The cart of a wholesaler's B2B portal: prices from the contractor's price list beside catalogue prices, warehouse stock and a credit limit the order goes over

What enova365 does by itself

First we check what does not need writing.

enova365 by itself

According to the vendor, with no code written:

Ready connections
  • Allegro
  • Shoper
  • PrestaShop
  • Magento
  • WooCommerce
  • Base
KSeF with no extra fees
  1. validation before sending
  2. a queue when KSeF is overloaded
  3. status tracking
Several stores at once
enova365 runs several online stores and B2B and B2C sales in one database.
Couriers in the program
Labels and tracking live in enova365, so we do not duplicate them in the integration.

Example: WooCommerce stays on the ready enova365 connection.

Custom integration

We add code only where your process goes beyond the ready connection.

  • A custom-built storeThe ready connections cover the platforms on the vendor's list.
  • A client panel or another company systemNeither the ready connection nor BaseLinker passes enova365 data there.
  • B2B rulesDiscounts, limits and kitting by your rules, which the ready connection does not know.

The B2B portal gets its own integration.

Three routes into enova365

From the simplest to the most flexible. We often combine two of them.

Ready enova365 connectionplatforms on the vendor's listThrough BaseLinkermany channels, one intermediaryCustom integrationyour system and your rules
A custom-built storeNoPartlyYes
Allegro, Shoper, WooCommerce and others listedYesYesYes
B2B rules: discounts, limits, kittingPartlyPartlyYes
Data for a client panelNoNoYes
Code neededNoNoYes
  1. Code needed (Ready enova365 connection): No, configuration.
  2. Code needed (Through BaseLinker): Usually not.
YesPartlyNo
"Partly" means it depends on configuration and version. We check it on your installation before quoting.

A B2B order from the portal to KSeF

A sample flow for a wholesaler with its own ordering portal. The KSeF invoice goes from enova365. enova365 is the source of truth for contractors, prices and stock.

  • B2B customer
  • Ordering portal
  • enova365
  • KSeF
  1. B2B customerOrdering portal

    Krok 1 z 7: Order from the cart

    Prices and credit limits from enova365

  2. Ordering portalenova365

    Krok 2 z 7: Order in the program

    The contractor matched by tax number

  3. enova365

    Krok 3 z 7: Picking and goods out

    On the warehouse side

  4. enova365KSeF

    Krok 4 z 7: Invoice to KSeF

    Validation and queueing in enova365

  5. KSeFenova365

    Krok 5 z 7: KSeF number

  6. enova365Ordering portal

    Krok 6 z 7: Status, document, KSeF number

  7. Ordering portalB2B customer

    Krok 7 z 7: Invoice in the client panel

Invoices and settlements for the wholesaler's customer

Invoices and settlements from enova365 are visible to the customer, with the KSeF number once accepted.

Invoices in a B2B portal on a phone: the amount due with the credit limit, an invoice waiting for its KSeF number and invoices with their KSeF numbers
  1. Amount due and the credit limit

    Settlements and the limit come from enova365. The credit limit is the amount a customer can buy up to without paying upfront, and the portal blocks orders above it.

  2. An invoice waiting for its number

    The customer sees the invoice at once, and its KSeF number appears only once it is accepted.

  3. The KSeF number on the invoice

    Once accepted, the number comes back from enova365 to the portal with the status and the document.

Who does what

enova365 is usually implemented by a vendor partner. We split the work so everyone does what they know.

You

  • Deciding which data is the source of truth.
  • Access to the program and a test environment.
    VulCode: tests on a data copy
  • Signing off test documents.

VulCode

  • The integration on your portal, store or panel side.
  • A queue, retries and an event log.
  • Tests on a data copy before launch.
    You: test documents to sign off

enova365 partner

  • Program setup, document types and series.
  • Turning on ready connections and KSeF.
  • Program licences and updates.

Common questions about enova365 integration

Answers about KSeF in enova365, implementation partners, WooCommerce and the integration code.

Where does enova365 stop in your company today?

Tell us what already connects to enova365 and what you retype by hand. We will reply within an hour with a proposal and a quote.