Procurement Contract Notice and Service Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: A procurement contract notice and service page is not "put an address in the contract". The website page should state: which matters require notice (orders/changes, lead time, quality claims, price adjustments, termination, force majeure, bank-account changes, disputes), to whom (notice address/contact/email/system), by what method (courier, registered mail, email, portal message, fax), when it takes effect (on arrival / on entry into the designated system / deemed receipt by agreement), how rejection, bounced mail or an address change is handled, and how evidence is kept. On the law: a non-dialogue declaration of intent takes effect when it reaches the counterparty; for a data message, if the counterparty designates a system, it takes effect when it enters that system, and if no system is designated, when the counterparty knows or should know it entered its system, unless otherwise agreed (Civil Code Article 137). Emails and other data messages that can tangibly express content and be retrieved at any time are treated as writing (Article 469). Termination requires notice, and the contract terminates when the notice reaches the other party; where the notice states automatic termination on a deadline, it terminates at the deadline (Article 565). A party unable to perform due to force majeure must notify promptly and provide proof within a reasonable period (Article 590). A reliable electronic signature has the same legal effect as a handwritten signature or seal (Electronic Signature Law Article 14). Electronic data includes emails, instant messages, communication records and login logs; the original should be provided, and authenticity is judged by the system environment, storage/transmission method and whether it was formed in the ordinary course of business (Evidence Provisions Articles 14, 15, 93 and 94). Courier companies must deliver to the agreed address, recipient or designated agent and inform them of face-to-face inspection (Courier Regulations Article 26). Information is current to 2026-11-07. This is a review of public rules and page practice, not legal or contract advice; the contract, the facts of service and the court's finding control.

This guide is for procurement, legal, finance, logistics, IT and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. This page most often misses who receives notice, at which address, when it arrives and how to prove it, ending up as "written notice shall prevail".

How does this page relate to contract signing, order change and termination pages?

The notice/service page answers "how to send, where, when it takes effect and how to prove it"; the contract/technical and quality agreement signing page answers document precedence, deviations, seals and versions; the order change/cancellation and expedite page answers change windows, costs and written confirmation; the force majeure and supply-disruption page answers clauses, notice, proof and mitigation. The notice page is the underlying rule for whether a notice is effective; a signing or change page cannot replace it.

Common breakpoints: the contract lists only the registered address while the office/receiving address differs; only a salesperson's personal email is given; sending the email is treated as service; a portal message has no "entered system" timestamp; the courier record has no recipient/time; the other side says it never received it; a termination notice is sent only by WeChat; force majeure proof is supplied long after the event. Separate "matter—recipient—method—effect—exception—evidence"; then procurement, legal, logistics and IT share one playbook.

This page map is editorial; the contract, the facts of service and the court's finding control.

Which matters require notice?

List the notice catalogue: orders/forecasts/lead time, order change/cancellation/expedite, quality nonconformity/claim/chargeback, price adjustment/reconciliation differences, payment/account change, termination, force majeure/supply disruption, IP/confidentiality, dispute/litigation. Each matter has a different deadline and consequence: a termination notice decides when the contract ends; a force majeure notice affects mitigation and liability; a quality objection affects claims; a price adjustment affects settlement. The page should provide "matter—deadline—recipient—method—template" rather than leaving staff to find an email.

Acceptance checks: matter list; deadlines; recipients; templates; escalation; records. Common gaps: only "major matters"; no deadlines; recipient is the salesperson; no templates; verbal notice; no record.

This list is editorial; the contract and business policy control.

How should methods and effective points be defined?

Choose methods that are provable, trackable and consistent with the contract: personal delivery (signature), courier/registered mail (waybill/tracking/signature), email (designated mailbox/headers), portal message (entry timestamp), fax (record), public announcement (only where law or contract allows). Effective rules: a non-dialogue declaration takes effect on arrival; a data message takes effect when it enters the designated system, or if none, when the counterparty knows or should know it entered its system; the parties may agree on the effective time (Civil Code Article 137). The page should state the effective point and evidence for each method, not "dispatch equals service".

Acceptance checks: method; designated address/mailbox/system; effective point; evidence; fallback; record. Common gaps: "written" only; no designated mailbox; no system timestamp; no fax record; abusive announcement; no fallback.

Effective rules follow Civil Code Article 137; the contract and the facts of service control.

How should notice addresses, contacts and changes be accepted?

The contract should state the notice address/contact/phone/email/system account and distinguish registered, office, receiving and invoicing addresses; the notice address may differ, but the contract must say which controls. Address/contact changes should be notified in writing with an effective date; if not notified, state the consequence of service to the old address (whether deemed served). Multiple contacts need primary/copy recipients; cross-border notices need time zone, language and method. The page may provide templates without publishing personal mobile numbers.

Acceptance checks: address types; notice address; contact; email; change; effect; multiple contacts; cross-border. Common gaps: registered address only; change not notified; contact left the company; personal email; no copy; no time zone.

This address/contact arrangement is editorial; the contract notice clause controls.

How should electronic service be accepted?

Electronic service should state: designated mailbox/system account, sender, recipient, subject format, attachment format, how entry into the system/mailbox is determined, whether auto-replies/read receipts equal service, how bounced mail/spam/capacity issues are handled, backup and logs. Civil Code Article 137 makes entry into the designated system the effective point for a data message; without a designated system, it is when the counterparty knows or should know it entered its system. The page should warn that "sent" is not "received" and provide secondary confirmation/fallback. Email is treated as writing (Article 469), but arrival and integrity still need proof.

Acceptance checks: designated system; sending/receiving accounts; timestamp; receipt; bounce; spam; backup; secondary confirmation. Common gaps: mailbox not designated; auto-reply treated as service; bounce not followed up; no logs; attachments altered; no fallback.

Electronic service follows Civil Code Articles 137 and 469; the contract and system records control.

How should deemed receipt, rejection and return be handled?

The contract may agree that sending to the designated address/mailbox is deemed service, but the agreement must be reasonable and workable, with evidence of actual sending; it cannot make every situation "dispatch equals service". If the other side rejects, the item is returned, the address is wrong or the mailbox is disabled: follow the contract (for example, deemed served on the return date), resend through a fallback channel and keep evidence. Public announcement is only for cases permitted by law or contract and cannot replace normal service. The page should state the sequence and evidence for rejection/return/address change/unreachable.

Acceptance checks: deemed-service clause; reasonableness; rejection; return; address change; fallback; announcement; records. Common gaps: dispatch equals service; no handling for rejection; return not followed; abusive announcement; no fallback contact.

Deemed service/rejection handling is editorial; the contract and the court's finding control.

How should evidence and record-keeping be accepted?

Notice evidence must prove who sent it, to whom, what was sent, when it arrived and that the content is unchanged. Common evidence: courier waybill + signature, registered-mail receipt, email headers (sender/recipient/time/server) + body + attachments, system log/timestamp, fax record, call recording, notarisation. Electronic data should be provided in original form; a copy consistent with the original or a printout directly from the original is treated as the original (Evidence Provisions Article 15); authenticity is judged by the system environment, storage/transmission method and ordinary-course formation (Article 93), and ordinary-course records, archival records and notarisation may be confirmed (Article 94). The page should state how long evidence is kept, where, and who can retrieve it.

Acceptance checks: evidence types; original; integrity; time; location; retention; retrieval; notarisation. Common gaps: screenshots only; emails deleted; attachments renamed; no headers; logs overwritten; incomplete recording; no archive.

Evidence requirements follow Evidence Provisions Articles 14, 15, 93 and 94; the rules of proof and the court's finding control.

How should termination notices be accepted?

Termination requires notice, and the contract terminates when the notice reaches the other party; if the notice states that the contract terminates automatically if the debtor fails to perform within a period, it terminates at the end of that period; the other party may ask a court/arbitration to confirm the effect; if the terminating party sues/arbitrates directly, the contract terminates when the copy of the complaint/arbitration application is served (Civil Code Article 565). The page should state the basis, content, method, arrival time, objection handling and post-termination settlement/transition. Do not write "sending the notice terminates immediately", and do not mix "negotiated termination/unilateral termination/automatic termination".

Acceptance checks: basis; content; service; arrival; automatic termination; objection; litigation service; transition. Common gaps: WeChat only; no basis; unclear arrival; unclear deadline; no objection handling; no handover.

Termination rules follow Civil Code Article 565; the contract and the court's finding control.

How should force majeure/supply-disruption notices be accepted?

A party unable to perform due to force majeure is relieved in part or in full according to the impact; it must notify promptly to mitigate the other side's loss and provide proof within a reasonable period; force majeure after delayed performance does not excuse liability (Civil Code Article 590). The page should state the notice deadline, content (impact, scope, expected recovery), proof types (government documents, incident certificates, transport/port certificates), mitigation, substitute performance and updates. Do not treat force majeure as a universal excuse or send notice long after the event.

Acceptance checks: deadline; content; proof; mitigation; updates; substitute; records. Common gaps: late; no proof; no updates; no mitigation; calling every disruption force majeure.

Force majeure notice follows Civil Code Article 590; the contract and the court's finding control.

How should electronic signatures and seals be accepted?

If notices/confirmations use electronic signatures, the page should state the signature type, authentication, signatory authority, timestamp, evidence/verification and loss reporting. An electronic signature is reliable if the creation data is exclusive to the signatory, controlled solely by the signatory at signing, and any change to the signature or the data message after signing can be detected (Electronic Signature Law Article 13); a reliable electronic signature has the same effect as a handwritten signature or seal (Article 14); the signatory must keep the creation data safe and, on loss or suspected loss, notify the parties and stop using it (Article 15). Do not treat an image signature or scanned seal as a reliable electronic signature.

Acceptance checks: signature type; authentication; authority; timestamp; evidence; verification; loss; contract. Common gaps: image signature; no authentication; unclear authority; no timestamp; cannot verify; loss not reported.

Electronic signature requirements follow Articles 13–15 of the Electronic Signature Law; the contract and certification-service rules control.

How should the notice/service page be written?

Suggested content: (1) applicable contracts/orders; (2) notice catalogue; (3) notice address/contact/email/system; (4) methods and effective points; (5) deemed service/rejection/return; (6) electronic service and logs; (7) evidence and archiving; (8) termination notices; (9) force majeure notices; (10) electronic signatures; (11) disputes/contact; (12) version and update date. The public page explains rules and entry points; it should not publish personal mobile numbers, system accounts or internal approvers; after login, parties can see their own notice records. State "the contract notice clause and actual service control"; do not write "dispatch equals service/mail is guaranteed".

Use consistent English terms (notice, service of notice, notice address, deemed receipt, delivery, email header, system log, termination notice, force majeure notice, reliable electronic signature) and state the review date. Link to contract signing, order change and force majeure pages, but do not turn the notice page into a signing page.

This structure is editorial; external statements must be truthful and verifiable, per the contract and actual service.

What must not be written?

High-risk claims: "sending the email is service" (arrival/entry into the system matters); "WeChat notice counts" (identity, content and arrival must be provable); "a deemed-service clause always works" (it must be reasonable, workable and backed by sending evidence); "rejection leaves no remedy" (follow the contract + fallback + evidence); "sending a termination notice terminates immediately" (on arrival); "force majeure is automatic relief" (prompt notice + proof + mitigation); "an image signature is an electronic signature" (reliability conditions apply); "publish all contacts" (personal/internal information). These are inaccurate or misstate service, effect or relief.

Safer wording: "This page applies to [contracts/orders]; matters [list]; notice address/email/system [per contract annex]; method and effect [arrival/entry into designated system]; rejection/return [handling]; evidence [waybill/headers/logs]; termination [basis/arrival]; force majeure [prompt/proof/mitigation]; e-signature [reliable/verify]. The contract notice clause and actual service control." External promotion must comply with advertising and fair-competition rules; contact information needs authorisation or redaction.

Go-live acceptance checklist

Ten checks: notice matters, notice address/contact, methods, effective rules, deemed service/rejection, electronic service, evidence archiving, termination notices, force majeure notices, e-signature and page wording. Each needs an owner, evidence and review date. The pass condition is not "the page says written notice", but that procurement, legal, logistics and IT can find the recipient, choose the method, prove arrival, handle exceptions and retrieve evidence from the page.

Before go-live, run one real (anonymised) notice through: draft → choose address/method → send → arrive → exception → evidence → archive. Any step that fails is a gap in the page or the process.

This checklist is editorial; the contract notice clause and actual service control.

Who should read this, who should not, and what decisions does it support?

It suits procurement, legal, finance, logistics, IT and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies building a notice page for the first time, or facing "notice not received / termination timing dispute / bounced email". It does not suit teams that trade only verbally, do not sign contracts, or want one page to replace legal/contract advice.

Read it if you are building a notice page; the contract lists only the registered address; only a salesperson's mailbox is given; sending is treated as service; the portal has no logs; termination is sent by WeChat; force majeure proof comes late. Skip it if you treat "sent" as "arrived", "read" as service, an image signature as reliable, or want to publish personal mobile numbers/system accounts. It supports self-review of matters, addresses, methods, effect, exceptions, evidence, termination, force majeure, e-signature and page wording.

FAQ

Is an email considered served once sent?

Not necessarily. Civil Code Article 137 provides that a data message takes effect when it enters the counterparty's designated system; if no system is designated, when the counterparty knows or should know it entered its system, unless otherwise agreed. "Sent" is only the sending act and is not the same as arrival. The page should state the designated mailbox, system logs, bounce handling and secondary confirmation.

Is a "deemed served" clause valid?

It may be agreed, but it must be reasonable and workable, with evidence of actual sending; it cannot make every situation "dispatch equals service". On rejection, return or a wrong address, follow the contract and resend through a fallback channel with evidence; public announcement is only for cases permitted by law or contract.

What if the other side rejects, bounces or changes address?

First follow the contract (for example, deemed served on the return date), verify the address/mailbox, resend through a fallback channel, and keep the returned item/bounce/tracking record. An address change should be notified in writing with an effective date; the consequence of serving the old address without notice should be stated in the contract.

When does a contract termination take effect?

Civil Code Article 565: the contract terminates when the termination notice reaches the other party; if the notice states automatic termination on a deadline, it terminates at that deadline; if the terminating party sues/arbitrates directly, it terminates when the copy of the complaint/arbitration application is served. The other party may ask a court/arbitration to confirm the effect.

Are WeChat/chat records written notice?

Emails and other data messages that tangibly express content and can be retrieved at any time are treated as writing (Article 469); instant-message records are electronic data (Evidence Provisions Article 14), but whether they prove arrival and integrity depends on identity, time, original medium and preservation. For important notices, also use the contract mailbox/courier and keep the original records.

Should the website publish notice addresses and emails?

It may publish the rules, address templates and entry points to help suppliers/customers prepare; do not publish personal mobile numbers, system accounts or internal approvers. After login, parties can see their own notice records; the public page states that the contract notice clause and actual service control.

One-sentence takeaway

A Changzhou manufacturer's procurement contract notice and service page is not "written notice shall prevail". It should turn notice matters, recipients, addresses/emails/systems, methods, effective rules, rejection/return, evidence archiving, termination, force majeure and e-signature into a reviewable checklist—so procurement, legal, logistics and IT can send it, calculate the effect and prove arrival.

Method and limitations

This is a review of public rules and page practice, not legal or contract advice. No undisclosed customer, contract, price or supplier data were used; processes, templates, tables and acceptance items are editorial, not legal conclusions. Notice effect follows Civil Code Articles 137, 469, 565 and 590; electronic signatures follow Articles 13–15 of the Electronic Signature Law; electronic evidence follows Evidence Provisions Articles 14, 15, 93 and 94; courier delivery follows Article 26 of the Courier Regulations; the contract, the facts of service, the rules of proof and the court's finding control.

Sources and scope

Information is current to 2026-11-07. The following are official pages; their text controls.

1. Civil Code of the People's Republic of China: Supreme People's Court. Effect of declarations (Article 137), written form (Article 469), termination notice (Article 565), force majeure notice/proof (Article 590).
2. Electronic Signature Law of the People's Republic of China (2019 revision): NPC website. Reliable signature conditions (Article 13), equal effect (Article 14), custody and loss reporting (Article 15).
3. Supreme People's Court Provisions on Evidence in Civil Procedure (2019 revision): Supreme People's Court. Electronic data scope (Article 14), original (Article 15), authenticity factors (Article 93), presumed authenticity (Article 94).
4. Courier Regulations (2025 revision): State Administration for Market Regulation. Delivery to the agreed address/recipient/agent with face-to-face inspection (Article 26).