Everything Brick already knows how to do.

How it works

1. 01From Integrations, each store connects its own Mercado Libre seller account through OAuth.
2. 02Listing conditions are built from Products: category, attributes, images and quantity, validated before publishing.
3. 03Brick links every listing to its variant, runs bulk operations and, when enabled, syncs inventory.

How it works

1. 01Each store is created by choosing its type, B2C or B2B, and a matching template.
2. 02Each one has its own channel, region, domain and identity, and Brick resolves the store for every request.
3. 03One core operates multiple brands or businesses without duplicating the platform.

How it works

1. 01The team creates and publishes articles from the admin.
2. 02Each article can connect products and media.
3. 03The storefront turns editorial content into a shoppable experience.

How it works

1. 01Build a cart with products and quantities from the back office.
2. 02Brick creates a shareable URL that preserves the selection.
3. 03Opening it restores the cart so the customer can continue to checkout.

How it works

1. 01An authorized user selects a table from the admin.
2. 02The backend validates the query and keeps the operation read-only.
3. 03Paginated data is returned for inspection without changing the database.

How it works

1. 01Each store configures its Analytics property and which events are sent.
2. 02Brick normalizes product, cart, checkout and purchase events and sends them server-side.
3. 03GA4 receives a consistent e-⁠commerce journey for analysis and attribution.

How it works

1. 01Customers add or remove products while browsing.
2. 02The selection is persisted against their account.
3. 03Wishlist restores the list so it can be resumed from another session.

How it works

1. 01The business defines rules, tiers, campaigns and rewards.
2. 02Purchases credit a ledger that supports reversals and expiration.
3. 03Customers see their points and redeem them in the storefront or checkout.

How it works

1. 01Choose the design, amount, recipient and delivery date.
2. 02Brick issues the gift card and manages delivery or its activation page.
3. 03Every use deducts balance and supports partial redemption until exhausted.

How it works

1. 01Create a campaign with the game, the prizes and the stores where it runs.
2. 02Visitors leave their email and play; the server validates each session and decides the result.
3. 03Prizes are issued as native promotions and the admin tracks participation and redemptions.

How it works

1. 01Each store connects its own Mercado Pago account and chooses which payment methods to offer.
2. 02Checkout creates the operation through Checkout Express or the embedded API.
3. 03Brick verifies every payment with Mercado Pago before confirming the order.

How it works

1. 01Each store sets up its own Mobbex account or uses the global one, and chooses whether to offer it at checkout.
2. 02Shoppers pay on Mobbex's hosted checkout and return to the store.
3. 03Brick re-checks the operation before confirming the order, and refunds run from the admin.

How it works

1. 01Each store connects its MODO account from Integrations.
2. 02At checkout, shoppers pay with the QR code or from their banking app.
3. 03Brick credits the payment only once MODO confirms it and expires stale QR codes.

How it works

1. 01Each store adds its GoCuotas account in Integrations and sets the minimum cart amount.
2. 02The shopper chooses installments and completes payment on GoCuotas checkout.
3. 03Brick creates the order only once GoCuotas confirms the charge, reconciles pending payments and issues partial refunds from the order.

How it works

1. 01Catalog changes trigger synchronization or reindexing.
2. 02Brick maps products and variants into searchable, faceted documents.
3. 03The storefront queries Typesense for instant search, filters and analytics.

How it works

1. 01Create a brand and connect it to its products.
2. 02Brick exposes active brands and preserves their catalog relationships.
3. 03The storefront enables brand pages, navigation and manufacturer filters.

How it works

1. 01Define the attribute dictionary with types, units and options, grouped into sets by vertical.
2. 02Each product gets its values from the admin or through CSV or Excel bulk upload.
3. 03Each store picks which attributes it uses and the product page shows the spec sheet.

How it works

1. 01Design a banner with placement, content, CTA, audience and schedule.
2. 02The API decides which piece applies to each store and moment.
3. 03The storefront renders it in the selected placement with its configured action.

How it works

1. 01The team uploads images and files once and organizes them with tags.
2. 02From the admin they can be cropped, resized and watermarked.
3. 03Editors filter and pick those assets from other modules without uploading them again.

How it works

1. 01The admin defines identity, contact details and preferences for each store.
2. 02Brick serves the configuration for the active domain or tenant.
3. 03The storefront adapts branding and behavior without code changes.

How it works

1. 01Register locations with address, hours, contact details and status.
2. 02Brick publishes enabled locations for each store.
3. 03The storefront uses them for information, pickup or coverage rules.

How it works

1. 01Customers complete the storefront form.
2. 02Brick validates and stores the request with its context.
3. 03The team receives it in the admin and through the configured notification.

How it works

1. 01Customers submit a review linked to a product.
2. 02The comment follows the configured moderation status.
3. 03Only approved reviews are published and enrich the catalog experience.

How it works

1. 01Upload a scene and place hotspots on the image.
2. 02Each point is linked to a specific catalog product.
3. 03Customers explore the scene and open or buy the highlighted products.

How it works

1. 01Publish a PDF and define hotspots on each page.
2. 02Hotspots can link products, videos or additional content.
3. 03The storefront presents it as an interactive, shoppable flipbook.

How it works

1. 01Connect Vimeo or synchronize an available video.
2. 02The team links the content to catalog products.
3. 03The storefront plays the video and surfaces products without breaking the journey.

How it works

1. 01The team composes a page from reusable blocks.
2. 02The landing page is drafted, previewed and then published.
3. 03Its slug resolves the active version with store content and products.

How it works

1. 01Edit and preview a transactional template from the admin.
2. 02The published version combines branding with event data.
3. 03The relevant workflow renders and sends the email through the configured provider.

How it works

1. 01Visitors submit their email in the storefront.
2. 02Brick records the subscription under the correct store.
3. 03When Brevo is configured, it also syncs the contact to its list.

How it works

1. 01Benefits are synced from Mercado Pago, Mobbex and MODO, or added manually by bank, installments, discount and schedule.
2. 02Brick evaluates which benefits apply to the current cart and time.
3. 03The storefront communicates valid options on product and checkout screens.

How it works

1. 01The business configures plans, frequencies, offers and commitment rules.
2. 02Customers subscribe and the scheduler creates every renewal and payment.
3. 03Self-service, dunning, retention and metrics cover the full lifecycle.

How it works

1. 01Brick detects identified carts that became inactive.
2. 02A workflow schedules reminders according to business rules.
3. 03Email or WhatsApp returns the customer to a recoverable cart.

How it works

1. 01Workflows consolidate sales, orders and customer behavior.
2. 02The API serves indicators and time series for the selected period.
3. 03The admin presents an operational e-⁠commerce dashboard.

How it works

1. 01The business defines segments through customer data rules.
2. 02Brick automatically evaluates and updates group membership.
3. 03Prices and promotions target the segment without manual lists.

How it works

1. 01A company registers and the team approves its account, members and terms.
2. 02Brick applies the customer's price list, credit, minimums, permissions and fiscal documents.
3. 03Buyers place quick or repeat orders; in order-taker mode they submit them for the team to approve, adjust or reject.

How it works

1. 01Enable a corporate experience on top of a B2B account.
2. 02Configuration adapts catalog, terms and access to each organization.
3. 03Employees and managers place orders within their commercial permissions.

How it works

1. 01Define locations, zones, fleet, drivers and dispatch rules.
2. 02Orders become routes that can be assigned and optimized.
3. 03The team and customer track delivery through completion.

How it works

1. 01Configure Andreani credentials and enabled services.
2. 02Checkout quotes options while the order creates the shipment and label.
3. 03Tracking events return to Brick to communicate delivery status.

How it works

1. 01Connect Paqar or MiCorreo with the account's services.
2. 02Checkout quotes home or branch delivery and the order creates shipment and label.
3. 03Brick reads tracking updates and keeps the delivery journey current.

How it works

1. 01Connect the envia.com account and choose the carrier for each warehouse.
2. 02Checkout quotes with that carrier using a fixed-box model or product dimensions.
3. 03The order ships with the chosen carrier: OCA, Correo Argentino, Urbano or another enabled one.

How it works

1. 01From Integrations, connect Bsale, Contabilium, Odoo or Zeus for the whole instance or a single store, and define its mapping.
2. 02Jobs synchronize products, images, stock, prices, lists and dimensions with traceability.
3. 03When payment is captured, Brick requests invoicing and records errors or retries; with Odoo, fulfillment updates the order.

How it works

1. 01The company uploads its fiscal certificate as a PDF.
2. 02Brick keeps versions, extracts its reference and enables comparison.
3. 03The back office and B2B account can access the relevant history.

How it works

1. 01Connect Kapso, the phone number and Meta-approved templates.
2. 02Bindings connect business events to the right message, and flows build guided conversations.
3. 03Brick sends notifications, handles support from the storefront button and lets customers check orders or buy from the chat.

How it works

1. 01The team builds each bot in a visual flow editor and publishes it to a store's web chat.
2. 02The bot answers, guides the purchase and can hand off to an AI agent with commerce tools.
3. 03When a person is needed, the conversation moves to the admin support inbox.

How it works

1. 01Operators ask the assistant from the back office with store context.
2. 02Tools and agents turn intent into concrete queries or workflows, within what their role allows.
3. 03The team receives operational results and actions without leaving the admin.

How it works

1. 01Upload products or barcodes for bulk enrichment.
2. 02AI proposes copy, attributes, data and images for each reference.
3. 03The team reviews and confirms before applying catalog changes.

How it works

1. 01The crawler scans pages and compares their content with the catalog.
2. 02Engines calculate findings, SEO score and visibility in AI answers.
3. 03The team simulates, prioritizes and applies fixes before auditing again.

How it works

1. 01Catalog, browsing and orders feed relationships and commercial signals.
2. 02The engine scores similar, complementary, popular and bought-together items.
3. 03Widgets render the results on product and cart pages, filtered by stock and channel, and track attributed revenue.

How it works

1. 01The team builds space templates with real catalog furniture and equipment.
2. 02Shoppers explore the space in a 3D editor and adjust allowed quantities or components.
3. 03The selection goes into the native cart or is sent as a quote request.

How it works

1. 01Connect each store's Microsoft Clarity project.
2. 02The storefront only records sessions once the visitor has consented.
3. 03The admin shows that store's metrics for the last 72 hours.

How it works

1. 01Choose the store and the stock location that feeds the catalog.
2. 02Brick generates an XML feed with variants, the final cart price (tax and promotions included) and real availability.
3. 03Google Merchant Center consumes it for Shopping and, when enabled, the same catalog is exported for OpenAI.

How it works

1. 01Connect the Meta Pixel and enable each store's catalog.
2. 02The storefront sends product, cart and purchase events to the Pixel.
3. 03Meta Ads consumes the catalog feed with the same prices and stock as Google Merchant.

How it works

1. 01Define cookie categories and banner copy per store.
2. 02Visitors accept, reject or choose by category, and their preference is stored.
3. 03Each banner revision asks again and scripts respect the choice.

How it works

1. 01Enabled per store; shoppers install or configure nothing.
2. 02The browser's AI assistant reads the store and uses WebMCP tools to search, build the cart and reach checkout.
3. 03Brick applies its usual price and stock rules, and a person always confirms the payment.