# Learning check

You are the solution architect for Zen Electron. The business has sent a new set of integration requirements, and you must recommend a design for each one.

The requirements are:

- **Gift with purchase**: Zenith Living wants to add a free accessory to any Cart above a set value.
- **Customer addresses**: the CRM team wants agents to edit Customer addresses in the CRM, while customers continue to edit them in the storefront.
- **Shipment updates**: the OMS sends a webhook each time a shipment leaves the warehouse.
- **Fraud screening**: Electronics High Tech wants every Order screened by a fraud service before it's saved, but the fraud service is sometimes unavailable.
- **Loyalty Connector**: a loyalty vendor has a marketplace listing but no public source repository.
- **Nightly report**: finance needs a report that takes about an hour to generate from Order data.

Use what you learned in this module to answer the following questions.

## Produce an integration recommendation

Before answering the questions, create a landscape plan for the six requirements. Use one row for each data flow and include:

- The built-in capability considered and why an integration is still needed, if applicable.
- The data domain and its source of truth.
- The direction and trigger.
- The connection point.
- One sentence each for the latency budget, idempotency strategy, and failure behavior.
- The runtime and the lowest viable adoption step.
- The implementation guide that owns the next step.

For the fraud-screening requirement, also record who can accept the risk of failing open and how an accepted but unscreened Order enters manual review. For the Customer-address requirement, show how edits from the non-owning system reach the source of truth without creating a bidirectional field sync.

Use the questions and feedback below to review the decisions in your plan. Revise any row where the selected connection point, contract, or runtime differs from the feedback.

## Next module

Continue the learning path by building Zen Electron's order confirmation email Connector from a template, then installing and operating it.

Build an order confirmation Connector from the official email template, publish it privately, then install and operate it as a Client.

## Related pages

- [Area overview page with navigation](/learning-integrate-with-commercetools.md)
- [Previous page: Plan your integration landscape](/learning-integrate-with-commercetools/integration-essentials/plan-your-integration-landscape.md)
- [Search documentation and API specs](/search.md)