{"id":1200,"date":"2026-02-25T10:37:27","date_gmt":"2026-02-25T10:37:27","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/"},"modified":"2026-02-25T10:37:27","modified_gmt":"2026-02-25T10:37:27","slug":"purchase-journey-bpmn-discovery-to-delivery","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/","title":{"rendered":"Purchase Journey: From Discovery to Payment and Delivery"},"content":{"rendered":"<p>When I first worked on a retail reengineering project, the team thought they had the customer experience mapped. But every time a customer abandoned a cart or failed a payment, the blame looped between marketing, IT, and fulfillment. That\u2019s when I realized: a journey isn\u2019t just touchpoints \u2014 it\u2019s a chain of decisions, responsibilities, and potential failures. The real power comes from modeling it all in BPMN.<\/p>\n<p>purchase journey BPMN isn\u2019t just about flowcharts. It\u2019s about making the invisible \u2014 handoffs, timeouts, logic \u2014 visible. You\u2019ll see exactly who\u2019s responsible when the system freezes during checkout, or why a delivery delay isn\u2019t just a logistics issue.<\/p>\n<p>This chapter walks you through building a full, practical BPMN model for an e-commerce purchase journey, starting from product discovery to delivery. We\u2019ll cover search, selection, checkout, payment, fulfillment, and common exceptions \u2014 all with real-world clarity. You\u2019ll learn how to structure it so that customer experience and process integrity coexist.<\/p>\n<h2>Mapping the Purchase Journey: Core Phases<\/h2>\n<p>Every purchase journey begins with a spark \u2014 a need, a desire, a search. But behind that spark lies a complex chain of digital and physical steps. We break it down into clear, manageable phases.<\/p>\n<ul>\n<li><strong>Discovery<\/strong>: Product search, browsing, and browsing behavior<\/li>\n<li><strong>Selection<\/strong>: Adding to cart, choosing variants (size\/color), price checks<\/li>\n<li><strong>Checkout<\/strong>: Shipping details, address validation, order summary<\/li>\n<li><strong>Payment<\/strong>: Payment processing, authorization, confirmation<\/li>\n<li><strong>Fulfillment<\/strong>: Order batching, warehouse pick, packing, carrier handoff<\/li>\n<li><strong>Delivery<\/strong>: Tracking, delivery attempt, successful handover<\/li>\n<li><strong>Exception Handling<\/strong>: Payment failure, out-of-stock, delivery delay<\/li>\n<\/ul>\n<p>Each phase is a gate \u2014 a decision point where the customer either moves forward or exits. The BPMN model doesn\u2019t just show the path; it reveals who owns what, when delays happen, and how the system recovers.<\/p>\n<h3>Designing for the Customer Experience<\/h3>\n<p>The customer doesn\u2019t care about backend systems. They care about speed, clarity, and reassurance. That\u2019s why modeling the purchase journey BPMN begins with empathy \u2014 not with the technology, but with the customer\u2019s perception.<\/p>\n<p>Place the customer as a primary lane or pool. This ensures every step reflects their experience. Use a dedicated lane for the customer, even if they\u2019re not the one executing tasks. If they\u2019re in the flow, they\u2019re part of the process.<\/p>\n<p>Here\u2019s a key insight: many models treat checkout as a single task. But in reality, it\u2019s a sequence of micro-decisions \u2014 address validation, payment method selection, security checks. Each one can become a bottleneck.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Phase<\/th>\n<th>Key Customer Experience Focus<\/th>\n<th>BPMN Support Strategy<\/th>\n<\/tr>\n<tr>\n<td>Discovery<\/td>\n<td>Relevance, speed, visual clarity<\/td>\n<td>Use message flows for search suggestions, timer events for auto-suggestions<\/td>\n<\/tr>\n<tr>\n<td>Checkout<\/td>\n<td>Frictionless, transparent, error prevention<\/td>\n<td>Use gateways for validation, send\/receive tasks for third-party checks<\/td>\n<\/tr>\n<tr>\n<td>Payment<\/td>\n<td>Trust, confirmation, security<\/td>\n<td>Use events for success\/failure, annotate with expected wait times<\/td>\n<\/tr>\n<tr>\n<td>Delivery<\/td>\n<td>Transparency, tracking, control<\/td>\n<td>Use message flows for carrier updates, timer events for delivery windows<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When modeling checkout and payment BPMN, treat the customer as a participant. Even if they&#8217;re not doing the work, they\u2019re waiting. A \u201cwaiting for payment confirmation\u201d task isn\u2019t just a delay \u2014 it\u2019s a moment of anxiety. Annotate it with expected timeframes and fallback actions.<\/p>\n<h2>Modeling the End-to-End Flow<\/h2>\n<p>Start with the customer\u2019s trigger: a product search. That\u2019s your <strong>Start Event<\/strong>. From there, map the logical flow, not just what\u2019s easy to automate.<\/p>\n<p>Break down the checkout process into subtasks:<\/p>\n<ol>\n<li>Customer selects product and adds to cart<\/li>\n<li>System checks inventory and availability<\/li>\n<li>Customer proceeds to checkout<\/li>\n<li>System validates shipping address<\/li>\n<li>Payment method is selected and processed<\/li>\n<li>Order is confirmed and sent to fulfillment<\/li>\n<li>Fulfillment begins: pick, pack, ship<\/li>\n<li>Carrier receives package, tracking number issued<\/li>\n<li>Delivery attempt made<\/li>\n<li>Success: customer receives package<\/li>\n<\/ol>\n<p>Use BPMN gateways to reflect decisions:<\/p>\n<ul>\n<li>Is inventory available? \u2192 Yes \u2192 proceed, No \u2192 notify customer<\/li>\n<li>Is payment valid? \u2192 Yes \u2192 confirm order, No \u2192 retry or fail<\/li>\n<li>Is delivery address valid? \u2192 Yes \u2192 ship, No \u2192 prompt correction<\/li>\n<\/ul>\n<p>For complex flows like order to delivery customer journey, use a <strong>Sub-Process<\/strong> for fulfillment to keep the main flow readable. Break it into steps: order received \u2192 warehouse validation \u2192 pick \u2192 pack \u2192 handoff to carrier.<\/p>\n<p>Use <strong>Boundary Events<\/strong> to capture exceptions:<\/p>\n<ul>\n<li>Payment failed \u2014 <em>Event Subprocess<\/em> with retry logic<\/li>\n<li>Out of stock \u2014 <em>Cancel Order<\/em> and notify customer<\/li>\n<li>Delivery failed \u2014 <em>Resend<\/em> or <em>Hold for pickup<\/em><\/li>\n<\/ul>\n<p>These exceptions aren\u2019t afterthoughts. They\u2019re part of the journey \u2014 and modeling them in BPMN makes recovery plans visible and testable.<\/p>\n<h3>Channels and Touchpoints in BPMN<\/h3>\n<p>Customers interact through multiple channels: web, mobile, call center, in-store. Each one can trigger the same purchase journey \u2014 but the path might differ.<\/p>\n<p>Use <strong>lanes<\/strong> to represent channels. For example:<\/p>\n<ul>\n<li><strong>Web\/Mobile<\/strong>: Self-service checkout, digital payment<\/li>\n<li><strong>Call Center<\/strong>: Agent-assisted order entry, payment collection<\/li>\n<li><strong>In-Store<\/strong>: Cash or card payment, immediate pickup<\/li>\n<\/ul>\n<p>Group steps by channel. A single purchase journey can branch at entry based on channel. This doesn\u2019t mean creating multiple models \u2014 it means using lanes to show where responsibility shifts.<\/p>\n<p>Use message flows to represent communication between channels and backend systems. For instance, the mobile app sends a <em>create order<\/em> message to the API, which then triggers fulfillment.<\/p>\n<p>Keep it clean. Avoid cluttering the model with redundant tasks. If the core logic is shared, model it once in a sub-process and reuse it across lanes.<\/p>\n<h2>Handling Exceptions: When the Journey Breaks<\/h2>\n<p>Most models show the \u201chappy path.\u201d But in reality, 30% of purchases fail at some point \u2014 payment issues, stockouts, delivery problems. These are not edge cases. They\u2019re central to the customer experience.<\/p>\n<p>Here\u2019s how to model common exceptions in purchase journey BPMN:<\/p>\n<h3>Payment Failure<\/h3>\n<p>Use a <em>Boundary Event<\/em> on the <em>Process Payment<\/em> task. If the bank rejects the transaction:<\/p>\n<ul>\n<li>Offer retry (max 2 attempts)<\/li>\n<li>After 3 failed attempts, mark order as abandoned<\/li>\n<li>Send notification: \u201cWe couldn\u2019t process your payment. Please try again.\u201d<\/li>\n<li>Option: allow switching to alternative payment method<\/li>\n<\/ul>\n<p>Use a timer event to close the retry window. Don\u2019t leave customers stuck in an infinite loop.<\/p>\n<h3>Out-of-Stock or Unavailable Item<\/h3>\n<p>When inventory is low, use a gateway to check stock. If unavailable:<\/p>\n<ul>\n<li>Notify customer immediately<\/li>\n<li>Offer substitution or refund<\/li>\n<li>Remove item from cart<\/li>\n<li>Update inventory system<\/li>\n<\/ul>\n<p>Model this as a conditional path \u2014 not error, but a valid decision.<\/p>\n<h3>Delivery Delay<\/h3>\n<p>Use a timer event on the <em>Shipment Sent<\/em> step to check delivery window. If delivery is late:<\/p>\n<ul>\n<li>Trigger a message to the customer: \u201cYour order is delayed.\u201d<\/li>\n<li>Update tracking status<\/li>\n<li>Escalate to customer support if beyond 48 hours<\/li>\n<\/ul>\n<p>Use a <em>Message Event<\/em> to receive updates from the carrier. This keeps the model aligned with real-world events.<\/p>\n<p>These exceptions aren\u2019t noise. They\u2019re opportunities. When modeled correctly, they reveal where the process is fragile, and where empathy must be built in.<\/p>\n<h2>From BPMN to Real-World Action<\/h2>\n<p>Once the model is built, it becomes a living document \u2014 not just a diagram for presentation.<\/p>\n<p>Use it to:<\/p>\n<ul>\n<li><strong>Identify bottlenecks<\/strong>: Where are delays happening? Is it address validation? Payment processing? Use swimlanes to see where handoffs take time.<\/li>\n<li><strong>Assign ownership<\/strong>: Each task should have a responsible role. If a task is \u201cunknown,\u201d the process is broken.<\/li>\n<li><strong>Measure performance<\/strong>: Attach KPIs like \u201caverage time to payment confirmation\u201d to tasks. Use BPMN to track SLA adherence.<\/li>\n<li><strong>Align teams<\/strong>: Marketing, IT, fulfillment, and customer service can all point to the same diagram to understand their role.<\/li>\n<\/ul>\n<p>Remember: a BPMN model isn\u2019t a report. It\u2019s a tool for conversation. When teams debate whether to retry a failed payment, they can point to the model and say: \u201cThis is the process.\u201d<\/p>\n<p>And when customer complaints spike after a change, the model helps trace the root cause \u2014 was it a new payment gateway? A delay in fulfillment? The model tells you.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I model a customer journey where they switch from mobile to web during checkout?<\/h3>\n<p>Model the journey once, using lanes to represent channels. The customer\u2019s path can cross lane boundaries. Use message flows to show transitions between systems \u2014 for example, from mobile app to web-based payment gateway. Keep the flow single, but show where channels interact.<\/p>\n<h3>Can I use the same BPMN model for both online and in-store purchases?<\/h3>\n<p>Yes \u2014 but with a twist. Use a <strong>Sub-Process<\/strong> for the core order flow (inventory check, payment, fulfillment). Branch the model at the start: one path for online, one for in-store. The core logic remains the same, but execution differs. This preserves consistency while allowing channel-specific behavior.<\/p>\n<h3>How do I show customer wait times in the BPMN model?<\/h3>\n<p>Use <strong>Timer Events<\/strong> to represent expected wait durations. For example, \u201cWait 5 minutes for payment confirmation.\u201d Use <strong>Message Events<\/strong> to represent real-time feedback. Annotate tasks with expected timeframes \u2014 e.g., \u201cFulfillment: 2\u20134 hours after confirmation.\u201d This helps teams manage expectations.<\/p>\n<h3>Should the customer be in a separate pool or lane?<\/h3>\n<p>Use a <strong>separate pool<\/strong> if you want to emphasize the customer\u2019s role as a distinct participant, especially in cross-functional models. Use a <strong>lane<\/strong> if the customer is part of a larger process (e.g., \u201cCustomer Service\u201d pool with \u201cCustomer\u201d lane). Choose based on clarity and audience.<\/p>\n<h3>How do I validate my purchase journey BPMN model?<\/h3>\n<p>Check for: completeness (all steps accounted for), correct flow (no missing paths), clear ownership (each task has a responsible role), and exception handling (failures are modeled). Use validation tools in your BPMN software (e.g., Visual Paradigm) to catch errors. Then run it by stakeholders: \u201cDoes this reflect what actually happens?\u201d<\/p>\n<h3>Can I automate parts of this flow using the BPMN model?<\/h3>\n<p>Absolutely. The BPMN model is a blueprint for automation. Tasks like \u201csend confirmation email,\u201d \u201ccheck inventory,\u201d or \u201cnotify fulfillment\u201d can be automated with workflow engines. Use the model to define triggers, conditions, and handoffs. But preserve human touch where it matters \u2014 like delivery exceptions or complaints.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first worked on a retail reengineering project, the team thought they had the customer experience mapped. But every time a customer abandoned a cart or failed a payment, the blame looped between marketing, IT, and fulfillment. That\u2019s when I realized: a journey isn\u2019t just touchpoints \u2014 it\u2019s a chain of decisions, responsibilities, and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1197,"menu_order":2,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1200","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Purchase Journey BPMN: From Discovery to Delivery<\/title>\n<meta name=\"description\" content=\"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Purchase Journey BPMN: From Discovery to Delivery\" \/>\n<meta property=\"og:description\" content=\"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/\",\"name\":\"Purchase Journey BPMN: From Discovery to Delivery\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:37:27+00:00\",\"description\":\"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"End-to-End Journey Examples in BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Purchase Journey: From Discovery to Payment and Delivery\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Purchase Journey BPMN: From Discovery to Delivery","description":"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/","og_locale":"pt_PT","og_type":"article","og_title":"Purchase Journey BPMN: From Discovery to Delivery","og_description":"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"8 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/","name":"Purchase Journey BPMN: From Discovery to Delivery","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:37:27+00:00","description":"Master the ecommerce purchase process BPMN with a clear, customer-centric BPMN model that covers checkout and payment BPMN, order to delivery customer journey, and real-world exceptions.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/purchase-journey-bpmn-discovery-to-delivery\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"End-to-End Journey Examples in BPMN","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/"},{"@type":"ListItem","position":4,"name":"Purchase Journey: From Discovery to Payment and Delivery"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1200\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1197"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1200"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}