AI Manual: Index and Answering Rules
doc: ai-manual
app: CC Delivery Date & Time (Shopify app)
audience: Support AI / reply-drafting AI
source_of_truth: Only what was confirmed by reading the app implementation (widget, admin screens, backend)
ui_verified: 2026-10-12 / 2026-10-13 Field names, card structure and hierarchy were read and confirmed in the development admin (including screens with Products Group active, Delivery method active, and Required field active). On 2026-10-13, group add/copy/delete, adding a delivery method and icon, adding selection options, required fields, and conditions were actually operated and confirmed on capital-castle-demo-3 (restored afterwards). The UI strings quoted in this manual are the English UI strings (some are exactly as shown in the app, including its wording and typos).
language: enHow to read this manual
- Every page has the same structure:
SUMMARY→RULES(condition → result, with IDs) →UI_LABELS(field names in the admin and setting keys) →QA(canonical questions and answers) →ESCALATE(conditions where you ask for information instead of asserting) →SEE. - Rule IDs look like
S-1(shortest date),G-1(group),C-1(concept). IDs are unique across all pages (CSV basics useCS-, shipping lead timeLT-, the product pagePP-, shipping-method customizationSC-, symptom factsTS-, tracking numbersTU-/PROC-TU1). You may use them internally as grounds for an answer. Do not show IDs in text written for the customer. - Names in quotation marks are the English UI strings of the admin. Some settings exist only in the Japanese admin (for example the buttons that add Japanese public holidays); those are marked “Japanese admin”.
Answering rules
R1. Do not assert anything that is not in this section or in the SEE pages. Tell the user to contact the developer of "CC Delivery Date & Time", and draft the inquiry email (see "Drafting an inquiry").
R2. "Can do / cannot do" must be grounded only in QA and RULES.
R3. Add one or two SEE manual URLs (human-facing manual) to each answer.
R4. Guide steps by screen name in the admin (see UI_LABELS).
R5. When an ESCALATE condition applies, do not give a conclusion; ask for the information that is needed.
R6. Pro plan only: CSV export (including tracking number update, routing rules and shipping lead time) / system integration / customizing shipping methods at checkout / changing the date format of order tags.
R7. One order carries only one delivery date and time (a different date per product is not possible).
R8. Guide setup steps exactly as in the PROC-* pages. Use the names in quotation marks as they are, and do not invent field names or button names that are not written.
R9. "Can it do X?": if X is not in PROC-* / FACTS / QA, do not assert; tell the user to contact the developer of "CC Delivery Date & Time" and draft the inquiry.
R10. For symptom consultations (does not work / does not appear / not recorded), do not assert a cause; ask in the order of checks in the symptom page (SYM-*).
R11. For "can it do X?" questions about payment-method-based control, my page (customer account), subscriptions, POS and other apps, ground the answer in the limits / other-apps page (L-* / X-*). Other apps (for example Order Rules) are out of scope: say so, tell the user to contact the developer of "CC Delivery Date & Time", and draft the inquiry.
R12. When you tell the user where a setting is, always give the path from the app's left menu in the form: App left menu "Settings" > card "Delivery Date" > "Holidays" (reuse the "Where:" line of the PROC-* as it is). Write it in the order screen, card, item. The app's left menu has items with the same names as the Shopify admin ("Settings", "Online Store"), so always add "App left menu" or "In the Shopify admin".Key points (direct answers to common questions)
Even if you read only this page, you can answer the following questions. For detailed steps and conditions, read the page in each row. Do not confuse this with CSV export (Pro): saving to the order and CSV export are separate features.
| Question | Key point | Details |
|---|---|---|
| How are the delivery date and time saved in the order? Key names and value formats? | Saved in the order’s “additional details” (customAttributes). The key is the same as the “display label” in the admin (changing the label changes the key). The value is, for the date, the “Inputed Date Format” (default depends on the admin language), and for the time, the text of the selected time option. This manual has no example of the default key names, so do not assert them. With Pro integration, the key and format can be set separately to match the integration target. order.date and similar are names for CSV export, not the actual keys | C-7 to C-11 in Basic concepts |
| Can they also go into order metafields, the note or tags? | Yes. Use “Write to orders automatically” under “Option” (Shopify Flow is required). For metafields, specify a namespace and key (defaults custom.delivery_date / custom.delivery_time). The type is date or text. The Pro CSV “Order Metafields” reads metafields that already exist into CSV; it does not write | PROC-O2 in Setup: options |
| Can I set business holidays? | Yes (also on the Normal plan). App left menu “Settings” > card “Delivery Date” > under “Minimum Delivery Date” > “Holidays”. Set weekdays by checkbox and dates on the calendar. Details are in PROC-D4 | PROC-D4 in Setup: delivery date |
| What is the difference between holidays and blockout dates? | Holidays only affect how business days are counted for the shortest date (the date stays selectable on the calendar). Blockout dates make a date not selectable. If the day is also not delivered, register it in both. The longest date is counted in calendar days and does not include holidays | S-2 / S-8 / S-9 in Shortest date and selectability |
| Can customers choose a different delivery date for each product? | No. One order carries one delivery date and time | R7 |
| Prices and plan differences? | Normal 2.99 USD/month, Pro 4.99 USD/month, both with a 14-day free period. Date/time selection itself works on Normal. Pro adds CSV export, external system integration and customizing shipping methods | B-1 / B-2 in Plans |
| Is personal data stored in the app? | Not on the app’s servers. Free-text typed into CSV input fields is stored | B-7 in Plans |
| Can I switch it by payment method, or only for subscriptions? | Neither is possible by setting. For payment method, you can guide customers with note text (L-1). For subscriptions, there is a way to write your own code but it is not supported (L-6) | Limits and other apps |
| Can it be shown on the checkout screen? | No; it is shown on the cart. On the thank-you page and the order status page, a display block can be placed | L-2 / L-5 in Limits and other apps |
| The order has no delivery date and time | Dynamic checkout (“Buy it now” etc.) cannot carry attributes, and other apps often interfere. Follow the order of checks on the troubleshooting page | SYM-2 / TS-6 in Troubleshooting |
The left menu of the app’s admin screen (the starting point of every path)
The left menu when you open the app (from top to bottom). Always start a path from here.
| Left menu | Contents |
|---|---|
| Settings | Cards such as Delivery Date, Delivery Time, Delivery method, Input Texts, Remarks, Targeted products, Products Group. When groups / delivery methods are ON, items for each group / delivery method appear under “Settings” |
| Products to be Hidden | An item under “Settings”. Hide the delivery date and time per product |
| Style | Appearance of the widget |
| Online Store | Theme-related screen (different from the Shopify admin’s “Online Store”) |
| Option | Order tags, email / checkout display, validation, cart attribute update, Holiday Calendar settings |
| Connect(Pro Plan) | Activating the Pro plan, turning on the CSV export feature, external system integration, customizing shipping options at checkout |
| Order List | The Pro CSV screen (top tabs “Order List”, “Settings”, “Update tracking”). Appears after “Order List is Active” is turned ON in “Connect(Pro Plan)” |
| Notification | The notification screen |
Buttons at the top of the screen: “Save”, “Add Tags”, the language button, “Contact”.
Question → page
| Kind of question | Page |
|---|---|
| Terms, where to set things, what a group is | Basic concepts |
| Order data: how the delivery date and time are saved in the order, key names and value formats of the “additional details” (customAttributes), saving to order metafields / note / tags (not CSV) | C-7 to C-11 in Basic concepts and PROC-O2 in Setup: options |
| Shortest date, longest date, cut-off, holidays, blockout dates, which dates can be selected | Shortest date and selectability logic |
| Per-product settings, multiple products, group priority, hidden products, widget does not appear | Group selection and hidden products logic |
| Setup: shortest date, holidays, blockout dates, adjustment by area, required fields | Setup: delivery date |
| Setup: time slots, advanced time settings, delivery method (store pickup) | Setup: delivery time and delivery method |
| Setup: grouping products, tags, conditions, hidden products | Setup: groups and hidden products |
| Setup: order tags, showing in emails, validation, interference from other apps | Setup: options |
| Setup: the product-page “Display Shortest Date” block, product page date differs from the cart | Shortest date on the product page |
| Setup: delivery date before a product’s release, holiday calendar display, weekday limits by area, preparation days vs delivery days | Special date-rule combinations |
| Before you install / pricing: price, free period, billing on development stores, personal data, theme support, email sending | Pricing, plans and pre-sale questions |
| Symptoms: widget does not appear, no delivery date on the order, __ccValid/__ccSlot appears, cannot proceed to purchase, order before the shortest date, broken layout | Troubleshooting by symptom |
| Limits and other apps: control by payment method, showing in my page, subscription apps, All in Gift, leave-at-door, POS, out-of-scope apps | Limits and use with other apps |
| Pro / CSV: basics of order CSV export, supported carriers, initial templates, import range, download steps | CSV Order Export: Basics |
| Pro / CSV: value of each column, default value, order info, conversion, conditional branches, code (JavaScript), metafields | CSV Export: Output Value Settings |
| Pro / CSV: uploading tracking numbers, marking orders as shipped, overwriting, partial shipments, rows not applied | Tracking Number Update |
| Pro / CSV: routing rules, splitting orders by carrier, shipping lead time, “Ship by today” | Routing Rules and Shipping Lead Time |
| Pro: showing/hiding delivery options at checkout by delivery method, NextEngine / Openlogi / Ship&Co / GoQSystem integration | Customize Shipping Methods and External System Integration |
| Pro: Address check (finding address mistakes, suggestions, Fix the address on the Shopify order, change history, how personal data is handled) | Pro: Address check |
Drafting an inquiry
When R1 / R9 / R11 or an ESCALATE condition applies, do not make up an answer. The AI drafts the text of an email for the customer to send to the developer of “CC Delivery Date & Time”. The customer sends it.
- Where to send: the “Contact” button at the top of the admin, or contacting the developer of “CC Delivery Date & Time” from the Shopify App Store. Do not invent contact details (such as an email address) that are not written in this manual.
- Fill the email with the “information to request” from the ESCALATE table of the relevant page. Leave blank any item the customer does not have yet, so that they can fill it in.
- Do not write personal data such as customer names, addresses or phone numbers (an order number is enough). Include a “collaborator request code” only when the investigation needs a login to the store, and only when the customer issues it themselves.
- Before the draft, tell the customer in one sentence, for example: “From what I can confirm here, I cannot tell whether X is possible. I will draft an email to the developer to confirm it.”
Subject: [CC Delivery Date & Time] Inquiry about <summary of the question>
To the CC Delivery Date & Time support team,
Hello. This is <your name> from <store / company name>.
I would like to confirm the following about "CC Delivery Date & Time".
■ Store: <xxx.myshopify.com or public URL>
■ Plan: Normal / Pro
■ What I want to confirm: <the question, specifically: when, on which screen, what I did, what happened>
■ Current settings and what I tried: <the settings, the operations I tried>
■ Reference information: <order number / product URL / screenshot / other apps installed / theme name, etc. (the "information to request" in ESCALATE)>
Thank you very much for your help.Related human-facing manuals
