Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
ایک بار کی خریداری
ERPNext Allegro Connector
A build-to-order Frappe app that connects Allegro — Poland's largest marketplace — to ERPNext, syncing order import, offer publishing, inventory and price updates, shipping, and settlement reconciliation. ECOSIRE scopes, builds, installs, and supports it for your exact catalog and workflow.
$499.00USD
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
اہم خصوصیات
Allegro OAuth 2.0 authorization-code authentication with automatic token refresh via a Frappe `scheduler_events` job, stored in the `Allegro Settings` Single DocType
Scheduled Allegro order pull that deduplicates against `Allegro Order Log` and creates ERPNext `Sales Order` documents, with optional auto-generation of `Sales Invoice` and `Delivery Note`
Allegro checkout-form mapping: buyer, billing/shipping address, NIP/company data, and line items resolved to the correct ERPNext `Item` and `Customer`
Offer publish, edit, activate, and end operations driven from the `Allegro Offer` DocType linked one-to-one with ERPNext `Item`
Inventory sync from ERPNext `Bin`/`Stock Ledger Entry` back to Allegro offer quantity via a debounced `on_update` hook to prevent oversells
Price synchronization from a configurable ERPNext `Price List` to the matching Allegro offer price
Allegro delivery-method mapping (Smart!, One Box, courier, parcel locker) to ERPNext shipping rules and delivery documents
Settlement and fee import into an `Allegro Settlement` DocType, mapping commission and transaction fees for reconciliation against payouts
Whitelisted Frappe REST methods (`@frappe.whitelist()`) exposing sync actions for manual triggers and external automation
Idempotent, retry-safe sync jobs using Frappe's background job queue with backoff and structured error logging in `Error Log`
Role profiles and DocType permission rules separating offer publishers, order processors, and read-only viewers
Sandbox/production environment toggle in `Allegro Settings` so staging can be validated against Allegro's sandbox before go-live
Item-to-offer mapping table with category-parameter support so ERPNext attributes populate Allegro required parameters
Full request/response audit trail per sync with `hooks.py` doc-event wiring, kept upgrade-safe for Frappe/ERPNext v15 and v16
اس مصنوع کے بارے میں
If you sell on Allegro and run operations in ERPNext, the two systems live in separate worlds. Orders land in the Allegro seller panel, stock lives in ERPNext Bin and Warehouse records, and someone spends every morning rekeying orders, adjusting quantities across dozens of offers, and chasing why one listing oversold while another sat with hidden stock. ERPNext has no native concept of an Allegro offer, no awareness of Allegro's REST API, its checkout forms, or its Smart!/One Box delivery methods — so out of the box there is simply no bridge. Generic marketplace connectors tend to ignore Poland-specific realities like Allegro's OAuth flow, PLN settlements, commission and transaction fees, and the strict offer lifecycle Allegro enforces.
ERPNext Allegro Connector کیوں منتخب کریں
Allegro OAuth 2.0 authorization-code authentication with automatic token refresh via a Frappe `scheduler_events` job, stored in the `Allegro Settings` Single DocType
Scheduled Allegro order pull that deduplicates against `Allegro Order Log` and creates ERPNext `Sales Order` documents, with optional auto-generation of `Sales Invoice` and `Delivery Note`
Allegro checkout-form mapping: buyer, billing/shipping address, NIP/company data, and line items resolved to the correct ERPNext `Item` and `Customer`
Offer publish, edit, activate, and end operations driven from the `Allegro Offer` DocType linked one-to-one with ERPNext `Item`
Inventory sync from ERPNext `Bin`/`Stock Ledger Entry` back to Allegro offer quantity via a debounced `on_update` hook to prevent oversells
Price synchronization from a configurable ERPNext `Price List` to the matching Allegro offer price
ECOSIRE builds the ERPNext Allegro Connector as a proper Frappe app, not a pile of loose scripts. It ships as an installable app with dedicated DocTypes — Allegro Settings (a Single DocType holding OAuth credentials, environment toggle, and sync switches), Allegro Offer (linked to ERPNext Item), Allegro Order Log, and Allegro Settlement — plus mapping tables that translate your catalog and price lists into Allegro's structures. Authentication uses Allegro's OAuth 2.0 authorization-code flow with automatic token refresh driven by a scheduler_events hook, so the connection stays alive without manual re-login.
Technically, the connector integrates through hooks.py document events and Frappe's background job queue. Incoming Allegro orders are pulled by a scheduled job, deduplicated against Allegro Order Log, and materialized as ERPNext Sales Order (and optionally Sales Invoice / Delivery Note) documents with customer, address, and Allegro checkout-form data mapped in. Inventory flows the other way: a Stock Ledger Entry / Bin on_update hook debounces and pushes available quantity back to the matching Allegro offer through whitelisted server methods, so stock stays consistent and oversells are prevented. Offer publishing and edits (title, description, price, parameters, images) are driven from the Allegro Offer DocType, and price changes on your chosen ERPNext Price List propagate to Allegro. Allegro delivery methods (Smart!, One Box, courier) are mapped to ERPNext shipping rules, and settlement/billing entries are imported into Allegro Settlement so marketplace commission and transaction fees reconcile cleanly against payouts. Role profiles and permission rules scope who can publish offers versus who can only view orders, and every API exchange is logged for auditability. The app targets Frappe/ERPNext v15 and v16.
Because this is build-to-order, ECOSIRE does not hand you a generic download and wish you luck. We start with a short scoping call to map your Allegro account structure, catalog size, offer templates, tax and fee handling, and fulfilment model. We then build the connector against your ERPNext instance, validate it on a staging bench with your real (sandbox) offers, run UAT with your team, and cut over to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source, a git repository handover, documentation, training, and a post-go-live support window.
What you get
- Installable Frappe app source code for your ERPNext version (v15 or v16), branded and scoped to your catalog
- Installation and configuration on your ERPNext instance, including Allegro OAuth app setup and `Allegro Settings` wiring
- Technical documentation: DocType reference, hook map, scheduler jobs, and whitelisted method reference
- End-user guide plus a live training session for your offer-management and order-processing teams
- UAT on a staging bench against Allegro's sandbox, with a documented cutover and rollback plan
- Post-go-live support window for bug fixes and adjustments after production launch
- Git repository handover with full commit history so your team owns and can extend the code
- Field and parameter mapping sheet (ERPNext Item attributes to Allegro category parameters) for your product range
Who this is for
Polish Allegro seller on ERPNext
A CEE retailer or distributor whose orders originate on Allegro but whose inventory, invoicing, and accounting run in ERPNext. They need order import and stock sync to stop manual rekeying and prevent overselling across offers.
E-commerce operations manager
Owns the offer catalog and fulfilment. They want to publish and edit Allegro offers, sync prices from an ERPNext Price List, and map Smart!/One Box shipping to ERPNext delivery documents without living in the Allegro seller panel all day.
Finance / accounting lead
Responsible for reconciling Allegro payouts against commission and transaction fees. They need settlement data imported into ERPNext so marketplace fees map to accounts and margins are accurate.
ERP administrator / systems integrator
Maintains the ERPNext bench and needs a proper Frappe app — clean DocTypes, hooks, scheduler events, permissions, and a git repo — that survives v15/v16 upgrades rather than fragile one-off scripts.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the ERPNext Allegro Connector app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install ERPNext Allegro Connector and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How ERPNext Allegro Connector Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Allegro-specific fit | Built for Allegro's REST API, OAuth flow, offer lifecycle, and PLN settlements | Depends entirely on your developer's Allegro knowledge | Generic marketplace connector, rarely Allegro-aware | |
| Order import | Scheduled, deduplicated import to Sales Order with checkout-form mapping | Must be designed and built from scratch | Basic import, limited field mapping | |
| Inventory & price sync | Debounced two-way sync from Bin/Price List, oversell-safe | Achievable but you own all edge cases | One-way or polling-only, often no debounce | |
| Settlement & fee reconciliation | Allegro Settlement DocType maps commission and transaction fees | Rarely scoped in DIY budgets | Usually out of scope | |
| Architecture | Proper Frappe app: DocTypes, hooks, scheduler, permissions | Quality varies by developer discipline | Black-box app you cannot fully inspect | |
| Version support & upgrades | Targeted at v15/v16, upgrade-safe, git handover | You maintain it yourself | Vendor-controlled release cadence | |
| Support & ownership | Post-go-live window, full source, git repo you own | In-house or contractor dependent | Subscription/license, source usually locked | |
| Time to live | 2–4 weeks from confirmed scope, built and installed for you | Unpredictable, often months | Fast install but poor Allegro fit |
Frequently Asked Questions about ERPNext Allegro Connector
+Is this an instant download from the Frappe Cloud Marketplace?
No. The ERPNext Allegro Connector is build-to-order. ECOSIRE scopes it to your Allegro account, catalog, and fulfilment model, then builds, installs, and supports it. There is no self-service download — you receive tailored source and a git repository handover on delivery.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on catalog size, how many Allegro category parameters your offers use, tax/fee handling, and your fulfilment complexity. We confirm dates on the scoping call before any work begins.
+Which ERPNext versions are supported?
We build against Frappe/ERPNext v15 and v16. The connector is delivered as a proper Frappe app with upgrade-safe DocTypes and `hooks.py` wiring. Tell us your exact bench version on the scoping call and we target it precisely.
+What about support and updates after go-live?
Every build includes a post-go-live support window for bug fixes and adjustments. Because you receive full source and the git repo, your team can extend it independently, and ECOSIRE offers ongoing support or enhancement engagements — including adapting to Allegro REST API changes — as a separate agreement.
+How does it prevent overselling across Allegro and ERPNext?
Available quantity is the single source of truth in ERPNext. A debounced `on_update` hook on `Bin`/`Stock Ledger Entry` pushes stock changes to the matching Allegro offer through the Allegro REST API, so offer quantities track real stock and are reduced as orders and shipments post.
+Does it handle Allegro shipping and settlements?
Yes. Allegro delivery methods including Smart! and One Box are mapped to ERPNext shipping rules and delivery documents, and Allegro settlement/billing entries are imported into an `Allegro Settlement` DocType so commission and transaction fees reconcile against your payouts.
+Can you customize the field and offer mapping for our products?
Yes — that is the point of build-to-order. We map your ERPNext Item attributes to the required Allegro category parameters, configure which Price List drives offer pricing, and tailor the order-to-document flow (Sales Order, Invoice, Delivery Note) to how you actually fulfil.
Related Modules
قیمت کا تخمینہ طلب کریں
ERPNext Allegro Connector
A build-to-order Frappe app that connects Allegro — Poland's largest marketplace — to ERPNext, syncing order import, offer publishing, inventory and price updates, shipping, and settlement reconciliation. ECOSIRE scopes, builds, installs, and supports it for your exact catalog and workflow.
- Allegro OAuth 2.0 authorization-code authentication with automatic token refresh via a Frappe `scheduler_events` job, stored in the `Allegro Settings` Single DocType
- Scheduled Allegro order pull that deduplicates against `Allegro Order Log` and creates ERPNext `Sales Order` documents, with optional auto-generation of `Sales Invoice` and `Delivery Note`
- Allegro checkout-form mapping: buyer, billing/shipping address, NIP/company data, and line items resolved to the correct ERPNext `Item` and `Customer`
- Offer publish, edit, activate, and end operations driven from the `Allegro Offer` DocType linked one-to-one with ERPNext `Item`