Make the next job easier.

Bring your existing shop into your Daymerce workspace. You approve the connection in WooCommerce; your shop does not move to a new platform.

Use Today to choose the next useful task, rather than opening every part of your shop to find out what needs attention.

Keep the useful context with you when you are away from your desk. Start with a small task that fits the moment.

Let colleagues do their work with their own accounts and appropriate permissions. You keep ownership and access changes visible.

Put the customer, purchased items and order state together before you act. A payment status and a packing status describe different things.

Follow a packing round with products, quantities and special instructions together. You check the real parcel before confirming the order.

Keep an exception visible rather than marking an incomplete parcel as finished. A postponed order remains work to resolve.

Connect customer choices, lead times and delivery exceptions. Test the combinations your customers actually buy.

Prepare the product information, images and price together. Saving your work and publishing it to your shop are separate steps.

Use variants for choices that affect what the customer receives. Keep each real combination identifiable.

Keep the original image and let supported local optimisation prepare useful delivery variants. Check the result rather than judging only the file size.

Separate preparing work from applying it to WooCommerce and showing it to customers. Read the result at each stage.

Help a customer make a relevant next choice. Start with a small, deliberate relationship between products you know belong together.

Use Customer 360 to put purchases and recorded customer context together before answering or choosing a next step.

Use a template as a starting point, then check the facts and make the answer fit this customer. A prepared answer is not a sent message.

Record what the customer chose and which signup text was shown. Use that recorded preference when preparing marketing communication.

Bring the audience, offer and message into one plan. Start with a reason for the customer to care, rather than a discount for everybody.

Prepare a readable message with a clear purpose. Check its content and recipient experience before handing it to a sending workflow.

Make the trigger, audience, timing and intended action explicit. Treat a rehearsal as a check of the plan, not a real customer send.

Give returning customers a clear reason to participate. Start with rules you can explain and benefits your shop can actually deliver.

Use Content Studio to prepare pages and articles connected to what you sell. Brain can help prepare work where enabled; you remain responsible for the facts.

Use Insights to connect a number with its period, definition and supporting data. Growth is more useful when you can explain what changed.

Use confirmed purchase lines to support product cost estimates. Review the document and its product links before relying on the resulting margin picture.

Keep a reservation, its resources and payment information together. A booking is a different task from packing a physical order.

Use Care, described as Daycare on the website, to see available maintenance and content checks together. Open the evidence before changing anything.

Test the whole purchase path, including the rules and customer choices that your shop supports. Start with a real customer situation.

Use confirmed business details and published information pages as the basis for customer help. Keep private account details separate from public contact information.

Distinguish your personal Daymerce account from customer data belonging to a shop. Keep the scope and identity of a request clear.

Daymerce is a working layer connected to WordPress and WooCommerce through Edge. Document ownership per data type instead of treating synchronisation as a full database copy.

Edge connects the shop's approved WooCommerce capabilities to Daymerce. Treat installation, authorisation and feature verification as separate checks.

Separate organisation membership, shop access and permission to execute changes. Access to a screen is not permission to perform every action behind it.

Daymerce uses working views of shop information. Distinguish a connected installation from a completed import and from the current state of a particular record.

Use the shop's background queue for supported heavy work, with bounded jobs and progress. Normal visitor requests should not perform a long conversion themselves.

A separate storefront needs an explicit integration contract. The supported path checks the WooCommerce source, refreshes the frontend and verifies ordinary visitor HTML.

Start with the smallest affected task. Distinguish an unavailable Daymerce workspace, an unavailable WooCommerce source and a stale storefront.

Disconnecting revokes the Daymerce connection. It is a different operation from deleting stored data, removing Edge or undoing published shop configuration.