Features

Products, variants, attributes, images, categories, collections, brands, tags and custom fields live as one record in the panel. Data arriving from the ERP is normalised here, then converted into whatever shape each channel expects.

• Products, variants and attributes pulled from Nebim V3 and Paraşüt
• Per-channel title, description and image order
• Bulk editing, multiple languages and custom fields
• Product health check: missing images, missing attributes, duplicate models

Stock and price per variant, stock records per warehouse or store, and a pricing rule per channel. Exchange rates are refreshed regularly and multi-currency channels are converted here.

• Changed stock and prices are queued and pushed in batches
• A product drops to inactive on the channel when stock hits zero
• Automatic price conversion from the central bank rate
• Every change is logged with its old and new value

Order lines, shipments, billing and delivery addresses, payment method, status history and channel mapping are kept as separate records. Customer and address data is updated both ways with the ERP.

• Orders pulled from the channel, orders and invoices written to the ERP
• Courier integration records the shipment and tracking number on the order
• Cancellations, returns and partial shipments
• An order whose customer does not match stays on its own list — nothing is lost

Category, brand, attribute and option mappings; attribute aliases; tag rules. The platform reads your existing data and proposes mappings — the ones you approve become permanent.

• Map the ERP's “ANTRASİT” to the channel's “Anthracite Grey” once
• Nothing is pushed without a channel category — no silent failures
• Tag rules fill collections and campaigns automatically
• Unmapped values are reported before the push, not after

Push batches and their result reports, recurring error patterns, product health checks, duplicate cleanup, and stock comparison or export via Excel.

• Channel, ERP, command, consumer and exception logs, each on its own
• What each job ran with is stored, request and response body included
• The dashboard totals orders, revenue and failed jobs per channel
• Heavy work runs on a queue; neither the panel nor the channel slows down