DropUI

Match the message to shop, language, and customer role

OXID eShop often runs as multi-shop, B2B/B2C, with customer roles, customer-specific prices, quote, and ERP/PIM integrations. DropUI lets you test a storefront message for a concrete shop, language, role, threshold, or cart without changing pricing, checkout, or OXID logic.

Integration benefits

What you gain by connecting OXID eShop with DropUI

  • Scenarios for multi-shop, language, customer role, B2B, quote, and cart

  • Context-matched message without changing pricing, ERP/PIM, or checkout

  • Follow-up preserving shop, language, role, quote, and order condition

DropUI for OXID eShop: message aligned with shop context

In OXID eShop, one generic message quickly becomes too broad. Different shop, language, customer role, B2B process, quote, order threshold, or cart needs a different argument. DropUI adds a communication layer on the storefront, but does not change pricing, catalog, ERP/PIM, or checkout. That lets you test the argument without disrupting sales logic.

Customer role changes the decision

A B2B account may need clarification of quote, order condition, account manager, timing, or customer-specific price. A B2C shopper may respond to availability, delivery, code, or a simple cart return. In multi-shop, shop and language also have to be preserved. DropUI should speak to the concrete situation, not to the whole installation.

Follow-up without losing B2B, shop, and language

After consent, web push, email, SMS, or WhatsApp should return to the same shop, language, role, quote, product, cart, or order condition. If follow-up loses that context, it starts to feel like a random send, especially in B2B and multi-shop.

Judge the result inside the segment

Do not blend the whole installation into one average. Measure quote, form, add-to-cart, checkout, purchase, promotion use, and return separately by shop, language, role, or segment. Only then can you see whether the message truly helps the decision.

Integration data

Context you can use in your campaign

This data helps build DropUI scenarios in OXID eShop around shop, language, customer role, quote, cart, consent, and follow-up. Enable only the fields needed for a specific test.

  • Shop, language, product, category, variant, and process type
  • Customer role, B2B/B2C, account, price, or order condition
  • Quote, cart value, order threshold, and checkout stage
  • Traffic source, UTM, device, scroll depth, and exit intent
  • Contact and consent from the campaign form

Common questions

Questions about the OXID eShop integration

Do not mix context. The message should know shop, language, customer role, and process type because B2B, B2C, and different shops need different arguments.

When the decision involves quote, customer-specific price, order threshold, B2B account, account manager, or a process different from standard B2C purchase.

No. OXID still handles catalog, roles, pricing, cart, checkout, and integrations. DropUI tests the storefront message without changing store logic.

Return to the same shop, language, role, quote, product, cart, or order condition. Without that context, follow-up loses meaning quickly.

Separately by shop, language, role, or segment: quote, form, add-to-cart, checkout, purchase, promotion use, and return. A whole-installation average can hide the effect.

Connect OXID eShop with DropUI

Connect OXID eShop with DropUI and start from one context: shop, language, role, quote, order threshold, or cart.

Start free