AV Solutions Courier Shipping for WooCommerce

AV Solutions Courier Shipping for WooCommerce connects a WooCommerce store to Econt, Speedy, BOX NOW and Pigeon Express.

The plugin provides:

• Fixed or live contract checkout prices for delivery to an office, locker or address.
• Local office and locker lists, filtered automatically by the customer’s delivery city, with optional manual search.
• Courier address search with street or quarter selection and validation before an address-delivery order can be placed.
• WooCommerce Checkout Block fields for delivery locations.
• Contract price checks from the order screen without changing the order total.
• Shipment creation, PDF labels, automatic tracking history and cancellation.
• Courier, waybill and current delivery status fields in WooCommerce orders, customer order pages and outgoing order emails.
• Optional automatic completion of an order after the courier confirms delivery; returned and problematic shipments are flagged without automatic refunds or cancellation.
• Protection against accidentally creating a second shipment after an uncertain API response.
• Optional cash on delivery according to the merchant’s courier contract.
• Bulgarian sales documents for confirmed remote card payments, with a local QR code and PDF attachment.
• Documents for postal money transfer sales when supported by the merchant’s Econt or Speedy contract.
• An immutable document snapshot, a separate sequential document number and an event log. Newly issued sales documents include the courier, destination, waybill and delivery status available at issuance.
• Monthly audit XML exports validated against the included GPL-licensed schema.
• WooCommerce HPOS, classic checkout and Checkout Block compatibility.
• Merchant-defined shipping prices or live contract prices from the courier API, with percentage adjustment, minimum, maximum and fallback controls.
• Courier logos in the administration and responsive delivery-method cards in classic checkout and Checkout Blocks.
• Invoices, pro forma invoices and credit notes with sequential numbering and PDF output.
• Invoice-request and company fields in classic checkout and Checkout Blocks.
• Monthly Microinvest Delta TXT export and a ZIP archive of generated accounting documents.
• Bulk shipping-label and invoice generation from the WooCommerce orders list, without an artificial plugin limit.
• Optional customer delivery-history checks through Connectix and NepoStop.
• Optional VAT-number validation through VIES.
• Optional monthly audit XML email to the configured accountant.

The administration interface is in Bulgarian because the plugin is intended for Bulgarian stores. Shipping is limited to Bulgaria. Store owners must obtain their own courier API credentials and contracts.

Each courier can use a fixed merchant-defined checkout price or a live contract price from its API. Percentage adjustment, minimum, maximum and fixed-price fallback controls are available. The price-check button on an order remains a separate manual check and does not change an existing order total.

The plugin does not connect to a fiscal printer or submit files automatically to the Bulgarian National Revenue Agency. It can generate invoices, pro forma invoices and credit notes, but it does not guarantee legal or tax compliance. The merchant and their accountant must verify the configured company data, numbering, document layout, payment methods, VAT groups, postal money transfer contract and current reporting requirements before production use.

The bundled audit XSD is an independently authored validation subset for the XML generated by the plugin. It follows the publicly described Appendix 38 field structure, but it is not an official National Revenue Agency schema and its acceptance in the current reporting period has not been independently confirmed. Compare every export with the current official schema before submission.

External services

This plugin connects only to courier services explicitly enabled and configured by a store administrator. Enabling a courier and entering credentials authorizes the related API communication. No analytics or advertising services are used.

To synchronize delivery locations, search or validate a delivery address, obtain prices, create or cancel shipments, print labels and track shipments, the plugin may send the following data to the selected courier: sender account credentials and contact details; recipient name, telephone, email and delivery city, postcode, selected street or quarter, street or block number, address details or selected office; order reference and shipment number; package weight and dimensions; shipment content description; order currency and value; cash-on-delivery amount and options. Each courier processes this data under the merchant’s contract and its own terms and privacy policy. When automatic tracking is enabled, active shipment numbers are checked periodically through the selected courier API.

Econt

API requests are sent to demo.econt.com in the Econt test environment and ee.econt.com in production.

• API documentation: https://www.econt.com/developers/soap-json-api.html
• Privacy policy: https://static-content.econt.com/cms/pages/documents/privacy_policy/Politika_za_lichnite_danni_en.pdf
• General terms and customer information: https://www.econt.com/en/client-center

Speedy

API requests are sent to api.speedy.bg. Speedy uses the same API host with different test or production credentials.
The plugin also requests the contract-client list to load the client ID, name, object, contact, email and sender address available for the authenticated account. The sender telephone remains editable because it is not guaranteed in this response.

• API documentation: https://api.speedy.bg/api/docs/
• Privacy policy: https://www.speedy.bg/en/gdpr
• General terms: https://www.speedy.bg/en/terms-and-conditions

BOX NOW

API requests are sent to the HTTPS BOX NOW hostname configured by the administrator. The plugin accepts only boxnow.bg and its subdomains.

• API documentation: https://www.boxnow.bg/diy/eshops/api
• Privacy policy: https://boxnow.bg/en/personal-data-processing-notice
• Website terms and customer information: https://boxnow.bg/en/

Pigeon Express

API requests are sent to the HTTPS Pigeon Express hostname configured by the administrator. The plugin accepts only pigeonexpress.com and its subdomains.

• API documentation: https://api-docs.pigeonexpress.com/
• Privacy policy: https://pigeonexpress.com/privacy
• Service terms: https://pigeonexpress.com/terms

Connectix

When explicitly enabled, the plugin sends the customer’s telephone number and the configured API token to Connectix to request delivery-risk information. The result is stored with the WooCommerce order.

• API: https://api.connectix.bg/
• Terms: https://connectix.bg/bg/terms
• Privacy policy: https://connectix.bg/bg/privacy

NepoStop

When explicitly enabled, the plugin sends the customer’s telephone number and the configured API key to NepoStop to request delivery statistics. The result is stored with the WooCommerce order.

• API: https://nepostop.com/api/
• Website: https://nepostop.com/

VIES

When explicitly enabled and a VAT number is entered for an invoice, the country code and VAT number are sent to the European Commission VIES SOAP service. Results are cached for one day.

• Service: https://ec.europa.eu/taxation_customs/vies/

Privacy

The plugin stores courier credentials in the WordPress options table in encrypted form, using keys derived from the site’s WordPress salts. Credentials can alternatively be supplied as constants. Changing the WordPress salts requires the credentials to be entered again.

Order delivery details, courier shipment identifiers, tracking statuses and history, document snapshots, refund information and an action log are stored in the WordPress database. Generated customer document links are signed and expire after seven days. Anyone who obtains a valid link can open the document during that period, so links should not be published.

The plugin does not collect telemetry and does not send data to the plugin author. Data is sent to a courier only after that courier is enabled and configured, as described under External services. Store owners are responsible for adding the selected couriers and applicable retention information to their own privacy notice and for handling data-subject requests under applicable law.