Payment and Delivery Terms
Billing cycles, recurring payments, invoices and activation of the Nodali digital service.
1. Scope
These terms govern prices, billing periods, payment methods and activation of the Nodali digital service. The operator is David Hošek, doing business under the trade name Progity, Company ID 03956890, with registered office at U Potoka 247, 440 01 Peruc, Czech Republic, registered in the Czech Trade Licensing Register.
2. Prices and tax regime
Current prices are stated in the price list and in the order process. The operator is not registered for Czech VAT and is a VAT-identified person. For domestic customers the operator does not add Czech VAT to the price; the stated price is the amount charged by the operator. For cross-border B2B services, the tax regime is determined by the customer's registered office and tax status and other relevant circumstances; where the reverse-charge mechanism applies, the tax is declared by the customer in the recipient's state. The customer is responsible for the accuracy of the billing country, VAT/tax ID and other tax details. A change of the tax regime or prices applies only to future orders and periods in accordance with the announced conditions.
If the operator becomes registered for VAT, prices will be increased by VAT at the statutory rate from future billing periods onward. The change will be announced to customers in accordance with the procedure set out in the Terms and Conditions and will not affect billing periods that have already been concluded and billed.
3. Core and billing period
A Core billing period lasts one calendar month and starts at the activation time in the Europe/Prague time zone. It is a half-open interval including its start and excluding the start of the next period. The next period begins one month later at the same local time. If the corresponding day does not exist, it begins on the last calendar day of that month, and each later period is derived from the actual start of the immediately preceding period.
Example: activation on 10 July at 15:00 creates [10 July 15:00, 10 August 15:00). A period starting on 31 January continues on 28 February, or 29 February in a leap year, and the next period then starts on 28 or 29 March; it does not return to the 31st. Core is paid in advance on activation and in advance for each subsequent period.
4. Consolidated billing statement and objections
On the first day of the next billing period the operator issues one consolidated statement containing Core for the new period and add-ons for the closed period. It is always made available in the portal and sent as a mandatory service email to the tenant's main billing address and to the main administrator if different. Delivery cannot be disabled, although authorised recipients may be changed.
For card payments, an objection may be raised within 5 calendar days. If none is raised, payment is taken and a document issued on the sixth day. For bank transfer, an invoice with 14-day maturity is issued and objections may be raised until maturity. Portal estimates are informative; the final amount is determined when the period closes.
5. Core changes, billed unit and automatic upgrade
The billed unit is either one unique order or one unique shipment according to the customer's business model. It is selected at tenant activation, shown in the order, portal and statement, and cannot be changed retroactively. Re-imports, updates, status changes and technical duplicates of the same unit are not counted again. Under the order metric, an order with several shipments counts once; under the shipment metric, each unique shipment counts separately. A unit successfully accepted and processed remains counted even if later cancelled.
A voluntary upgrade or downgrade takes effect only from the next billing period. A downgrade may be scheduled no earlier than day six. The projection is units processed so far / elapsed billing days × total billing days in the period, rounded up; 5,000 units in 10 of 30 days therefore project to 15,000. A downgrade below the plan covering that projection is not permitted.
An automatic upgrade is scheduled for the next period if actual volume exceeds the current limit by more than 10% in one period, or exceeds it by at least one unit in three consecutive periods. A period at or below the limit breaks the sequence. The new plan is the lowest public plan covering the triggering volume. The consecutive-exceedance counter resets when the upgrade takes effect. Above the highest public plan, Enterprise pricing is not set automatically and must be agreed individually.
A voluntary change may be cancelled before it takes effect. An automatic upgrade cannot be cancelled; it is announced in the portal and by mandatory service email, and the customer may choose a higher plan or terminate Core at the end of the current period.
6. Recurring card payments
If the customer chooses recurring card payment, the customer consents to the use of a securely stored payment reference for future payments for active services. The operator does not store the full card number or the security code. The amount of a recurring payment may vary because it includes the Core price for the new period in advance and the proportional prices of add-on services for the ended period in arrears, plus any other items due. The billing date, active services and price are available in the portal. Before payment is made, the consolidated billing statement under Article 4 is always made available to the customer, including the period for objections.
The customer will be reasonably informed in advance of a change in the amount or frequency of the recurring payment. After each payment attempt, the customer will receive information about its result. The customer may switch off future renewals with effect from the end of the current period.
7. Bank transfer
For customers with bank transfer enabled, the invoice is issued on the first day of the new billing period together with the consolidated billing statement under Article 4, with a due date of 14 days unless agreed otherwise. Unless agreed otherwise, activation or continuation of the service may be conditional on timely payment. In the event of default, the service may be restricted or suspended after notice.
8. Documents
Upon a successful card payment, a corresponding accounting document is issued. For payment by transfer, an invoice with a due date is issued and its status is updated after payment in accordance with accounting rules. Documents are available in the tenant administration. Sending them by e-mail is governed by the tenant settings; the default setting is on.
9. Activation and delivery
Nodali is a digital service. Core, a module, a feed or another extension is activated without undue delay after the payment and technical conditions are met, usually within 24 hours. This does not apply where activation requires individual configuration, an individual integration, the customer's cooperation or integration approval; in such a case the date will be agreed separately.
10. Demo and individual trial
A public free trial is not a standard part of the offer. Functions can be tried in a demo environment with demo data. The operator may permit an individual trial in writing and may limit it in scope, duration or number of users.
11. Payment security
Card details are processed by a licensed payment service provider. The customer is responsible for the authorisation of the person making the payment and for the accuracy of the billing details.
The tax regime of a cross-border B2B service is determined by the billing country, the customer's status as a taxable person, the validity of the VAT or tax ID and other relevant circumstances. Indicative information displayed on the public website based on the visitor's country is not a binding tax assessment. The details confirmed by the customer at the time of the order are decisive.
12. Daily billing of add-ons
The governing time zone is Europe/Prague. Activation and deactivation take effect at the time recorded by the system and the active interval is [active_from, active_to). An active day is a local calendar date that overlaps the active interval at least partly. Activation and deactivation on the same date count as one active day; a date with no activity is not billed.
Billing days of a Core period are all local calendar dates that overlap that entire Core period at least partly. The daily price is the monthly add-on price divided by the number of those billing days. An add-on active for the entire period can therefore never exceed one monthly price. Rounding is applied only to the consolidated line item, not to each day in a way that systematically increases price.
Add-ons are billed in arrears in the next consolidated statement; activation does not cause a separate immediate card transaction.