LimeHippo Delivery and Receipts (UA)

Manage Ukrainian deliveries and fiscal receipts in one WooCommerce workspace. Connect Nova Poshta, Ukrposhta, Meest and Rozetka Delivery for shipping, and Checkbox or Vchasno. Kasa for receipts.

Keep shipments from different carriers together, work with several sender profiles and warehouses, and choose the appropriate cash register for each manual sale. You can start with an existing tracking number instead of creating a new shipment.

Delivery tools in Free

• Delivery methods for classic WooCommerce checkout and Checkout Blocks. Available branch, parcel locker and address delivery options depend on the carrier.
• Carrier connections and sender profiles, with no plugin-imposed limit on the number of saved shipments or profiles.
• Create an individual waybill using a sender profile, with optional order data loading and a review before submission to the carrier.
• Add an existing tracking number without creating another shipment at the carrier.
• A shared shipment list with recipient information, profiles, statuses, filters and pagination.
• Manual status checks, tracking history and individual waybill printing in the formats available through each carrier.
• Preliminary delivery quotes where supported by the integration. These are estimates, not a guarantee of the final carrier charge.
• CSV export with a date range.
• Links between WooCommerce orders and shipments, with delivery actions in the order list and order details.

Receipt tools in Free

• Manual receipts through Checkbox and Vchasno. Kasa, using your own connected and configured cash registers.
• Prepare a receipt from a WooCommerce order, or enter a manual sale without an order, including an offline sale or a shipment added separately.
• Edit the draft’s products, services, quantities, prices, discounts, register tax codes and payment details before issuing.
• Choose a receipt service and cash register for a manual sale, including registers belonging to different businesses.
• A receipt journal, manual status checks and access to available receipt documents.
• Full fiscal returns and manual shift management, subject to the service and register requirements.

Saving a draft does not issue a receipt, create a WooCommerce order or change product stock. Issuing a receipt is a separate action. A fiscal return does not refund money through a payment gateway, change the WooCommerce order or restock products.

Optional Pro add-on

The separately installed Pro add-on provides scheduled tracking, bulk shipment actions, CSV import, supported carrier account imports and bulk waybill printing. Receipt features include automatic issuing, register routing rules, automatic shift management, mixed payments, advance payments, partial returns, bulk receipt actions and receipt-name templates for products and variations.

Pro is optional. Free manual features and previously saved records remain available without an active Pro license. Carrier and receipt-service accounts, their fees and their access requirements are separate from the plugin.

Supported delivery options

• Nova Poshta: one domestic parcel from a branch to a branch, parcel locker or recipient address, within the integration’s size and weight limits.
• Ukrposhta: Standard or Express to a branch or address. A saved eCom sender and address are required for creation. Parcel locker delivery is not offered by this integration.
• Meest: supported domestic branch, parcel locker and address delivery. Availability depends on the selected destination and your contract.
• Rozetka Delivery: supported branch delivery.

Not every service exposes the same tracking, quoting, import or print operations. For example, preliminary API quotes are available for supported Ukrposhta and regular Meest routes; Nova Poshta, Rozetka Delivery and Meest parcel locker quotes are not currently offered. The interface and built-in help explain these differences.

Try the demo and get help

Open the interactive demo to explore fictional orders, shipments and receipts. The demo uses an isolated temporary store. Real carrier calls, email sending and fiscal issuing are disabled there. Its initial browser loading is specific to the demo, not the normal installed plugin.

The Support section contains first steps and FAQs grouped into general questions, delivery and waybills, and receipts and cash registers. Contact support@limehippo.com for assistance.

This is an independent integration. The named carriers and fiscal services are third-party services and are not the publisher of this plugin.

External services

This plugin integrates with six independent delivery and fiscal-receipt services. It does not send telemetry to LimeHippo. Saving credentials configures an integration; requests occur when you check a connection, use a service action, or enable its checkout method. Checkout city, street, pickup-point and rate searches contact the selected carrier as a shopper uses checkout. Responses may be cached locally. Creating a waybill, issuing a receipt, making a fiscal return and opening or closing a shift require a separate operator action in Free. Merely installing the plugin does not perform these writes.

All API calls originate from your WordPress server over HTTPS. The provider therefore also receives the server’s IP address and normal HTTP metadata. Use accounts and register credentials you are authorized to use. Provider fees, contracts and access requirements are separate from this plugin.

The service terms and privacy policy links below are published by each provider, usually on its public website rather than on the API hostname. They apply to the named integration. These pages are primarily in Ukrainian; Rozetka’s policy requires JavaScript to display. No acceptance of provider terms is performed by this plugin.

Nova Poshta

Purpose: city, branch and street selection, sender/connection checks, single-waybill creation, manual tracking and document printing.
Data: the selected merchant API key and directory search text or location IDs; sender and contact references for account queries; a tracking number or document reference for tracking/printing. After explicit creation confirmation, the service receives sender and recipient names, phone numbers, destination references or address, parcel description, weight/dimensions, declared value, payer and cash-on-delivery details. Creation also includes a local operation reference used to reconcile uncertain responses without resubmitting the shipment. Directory searches do not create shipments.
Endpoint: https://api.novaposhta.ua/v2.0/json/ . Printing sends the document number and API key to https://my.novaposhta.ua/orders/ . Tracking links open https://tracking.novaposhta.ua/ in your browser.
* Nova Poshta service terms, public agreement and API license
* Nova Poshta privacy policy
* Nova Poshta API information

Ukrposhta

Purpose: address and post-office directories, connection/sender checks, preliminary delivery quotes, single-waybill creation, manual tracking and printing.
Data: the configured bearer token and eCom token as required, directory text/region/city IDs, shipment barcodes, and parcel measurements/destination for quotes. Confirmed creation sends sender reference, recipient name, phone and address, parcel measurements, declared value, delivery type, payment and inspection options. Address/client/shipment writes are journaled; an uncertain result is not automatically recreated.
Endpoints: https://www.ukrposhta.ua/address-classifier-ws/ , https://www.ukrposhta.ua/ecom/0.0.1/ and https://www.ukrposhta.ua/status-tracking/0.0.1/ . Tracking links open https://track.ukrposhta.ua/ .
* Ukrposhta terms of service and public offer
* Ukrposhta privacy policy

Meest

Service provider: Meest Poshta (Trade House Meest Express LLC). This integration uses the provider’s api.meest.com API; its public legal documents are hosted on meestposhta.com.ua.

Terms of service: https://meestposhta.com.ua/storage/pdf/standartni_umovi_servisu.pdf
This is the actual Standard Terms of Service document (PDF), linked from the provider’s standard-terms page. Sections 1.1-1.4 explain its scope and relationship to the customer’s service agreement; the document also describes the Meest API service. Your own Meest account and applicable service agreement are required.

Privacy policy: https://meestposhta.com.ua/privacy-policy
The policy identifies Trade House Meest Express LLC as the provider and explains data processing for its services and account.

Purpose: cities, branches and supported courier streets, account checks, preliminary quotes, single-waybill creation, manual tracking and printing.
Data: the configured token/session, or login/password and agent details when obtaining a session; contract ID where required. Directory requests send search text and location IDs. Quotes send destination and parcel parameters. Confirmed creation sends sender and recipient contacts, branch/address details, parcel contents/measurements, declared value and payment options. Tracking/printing sends the shipment reference. Read-only parcel-list queries reconcile uncertain creation results; the plugin does not automatically repeat creation after a timeout.
Endpoint: https://api.meest.com/v3.0/openAPI/ . Tracking links open https://t.meest-group.com/ .
* Meest terms of service – direct PDF
* Meest page linking to the terms document
* Meest privacy policy
* Meest API documentation

Rozetka Delivery

Service provider: Terminal Rozetka LLC (company number 33584049), operating ROZETKA Delivery. The integration uses rz-delivery.rozetka.ua/api, which is linked as the API documentation from the provider’s help centre. Public customer and privacy documents are hosted on rozetka.delivery and help.rozetka.delivery, not on the API hostname.

Terms of service and account agreement: https://help.rozetka.delivery/p28-registration-process.html
ROZETKA Delivery supplies its logistics-service terms through an individually signed agreement with each business customer. Step 2 of this official page requires that agreement; the page is an explanation of access requirements, not a publicly published copy of the agreement. Obtain and review your contract with Terminal Rozetka before configuring its account in this plugin. Installing this plugin does not create an account or accept that contract. The provider does not link a public specimen of the individual agreement from this onboarding page.

Privacy policy: https://rozetka.delivery/auth/registration/rules
This is the provider’s full “Regulation on the processing and protection of personal data of users of the online platform”, dated 16 July 2024. It is a JavaScript-rendered page. Sections 1.1 and 1.5 identify Terminal Rozetka LLC; section 1.1 covers the website, app and related services/tools; sections 2-6 describe the data, processing purposes, disclosure and protection. It is not merely a registration form.

Purpose: city and branch selection, connection/sender checks, single-waybill creation, manual tracking and printing.
Data: public directory requests send only city/branch search text, location IDs and pagination. Authenticated operations use the selected partner token or account session; phone/password authentication obtains or refreshes that session. Confirmed creation sends sender/recipient contacts, branch references, parcel contents, weight/dimensions, declared value, payer and cash-on-delivery amount. A local operation reference is sent in visible_id to reconcile interrupted results without repeating creation. Tracking/printing sends the shipment reference.
Endpoint: https://rz-delivery.rozetka.ua/api/ . Directory requests use /city and /department; confirmed creation uses POST /track. Tracking links open https://rozetka.delivery/ .
* Rozetka Delivery service access and contract requirements
* Rozetka Delivery packing rules
* Rozetka Delivery services and tariffs
* Rozetka Delivery privacy policy
* Rozetka Delivery API documentation

Rozetka’s public onboarding page requires a separate signed logistics-services agreement. Your individual agreement supplies the contractual terms for the API account; the packing-rules page is not a substitute for that agreement. The privacy policy is published by Terminal Rozetka for the Rozetka Delivery platform, while API requests use rz-delivery.rozetka.ua.

Checkbox

Purpose: register connection checks, manual shift operations, issuing fiscal receipts, checking existing receipts, obtaining receipt documents and full fiscal returns.
Data: the selected register license key and cashier PIN when signing in; the resulting session token for authorized actions. A connection check reads register status and does not open a shift or issue a receipt. Confirmed issuing sends item names/codes, quantities, prices, discounts, tax codes, payment amounts/types and supported terminal/payment details, plus a saved operation UUID. A return also references the original receipt. Shift actions send register/session identifiers and the requested operation. Status and document requests send existing receipt IDs. Fiscal issuing does not request a buyer notification or send the buyer’s email/phone to Checkbox.
Endpoint: https://api.checkbox.ua/api/v1/ . Operations include cash-registers/info, cashier/signinPinCode, shifts and receipts/sell. Uncertain fiscal operations are checked by their original IDs before further actions.
* Checkbox terms of service and public offer
* Checkbox privacy policy
* Checkbox API documentation

Vchasno.Kasa

Purpose: register checks, manual shift operations, issuing fiscal receipts, status/document access and full fiscal returns.
Data: the selected service token in the Authorization header, register and operation references, and, for confirmed fiscal operations, item names/codes, quantities, prices, discounts, tax groups, payment amounts/types and supported payment details. A return references the original fiscal receipt/register/date. A connection check sends fiscal task 18 (status); it does not issue a sale or change the shift. Confirmed issuing uses task 1 and a return uses task 2. A saved operation tag supports read-only reconciliation after an uncertain result. Fiscal issuing does not send buyer email/phone or request a customer notification.
Endpoint: https://kasa.vchasno.ua/api/v3/fiscal/execute and related status/document endpoints on https://kasa.vchasno.ua/ .
* Vchasno.Kasa terms of service and public offers
* Vchasno.Kasa privacy policy
* Vchasno.Kasa API documentation

Email, linked documents and the optional Pro add-on

Email is sent through your site’s WordPress mail service only after an authorized user explicitly submits the support form or confirms sending an issued receipt link to one email address. The support form sends the entered message, reply address and plugin version to support@limehippo.com. The receipt email sends the selected document link to the chosen recipient. Your site’s mail provider processes those messages; the plugin does not silently subscribe customers or send their email to the carriers or fiscal services.

Opening a carrier tracking link or a provider-hosted receipt/document sends a normal browser request to that provider. The URLs above identify the relevant services and their policies.

The Free package contains no Freemius SDK or licensing request. A separately installed Pro add-on uses Freemius for license activation, synchronization and updates, as disclosed by its activation screen and readme. Pro also adds configured scheduled/bulk operations and supported read-only carrier account imports using the same service endpoints and saved accounts. Those implementations are not included in this directory package.