Method and system of online shopping via third party using blog

A method of online shopping comprising the steps of:

• at a seller:
• using a seller terminal (21) to access a seller blog (31) over the Internet (6);
• creating a plurality of item description web pages (3W1) in the seller blog (31) wherein at least one picture and accompanying description of at least one item being sold are posted on each of the item description web pages (3W1);
• using the seller terminal (21) to access a platform server (41) of an online billing platform (4) via the Internet (6);
• gaining access to a member web page (42W) of a login server (42) of the online billing platform (4);
• applying for membership;
• gaining access to the platform server (41);
• linking to the login server (42);
• logging in for gaining access to a program database (461);
• copying program codes of a sales agent tab program (P1) to the seller terminal (21);
• using the seller terminal (21) to link to the seller blog (31);
• copying the program codes of the sales agent tab program (P1) to the seller blog (31);
• installing a payment tab, a guide tab, and the program codes of the sales agent tab program (P1) in each of the item description web pages (3W1);
• clicking the guide tab of the item description web page (3W1) for linking to the platform server (41);
• linking to the login server (42);
• logging in for linking the seller to an item server (43) of the online billing platform (4);
• downloading the at least one picture and accompanying description of the at least one item being sold on the item description web page (3W1) to a merchandise database (431) of the item server (43);
• creating a merchandise file (431D) in the merchandise database (431);
• creating tab program codes (PC) in the program database (461);
• obtaining the tab program codes (PC) by linking to the program database (461);
• using the seller terminal (21) to link to the seller blog (31) and copy the tab program codes (PC) to the seller blog (31);
• and
• creating a plurality of merchandise sale web pages (43W1) having a payment tab and a link tab by the merchandise file (431D);
• at a buyer:
• clicking the link tab of the merchandise sale web page (43W1) to link the platform server (41) to the item description web page (3W1) for viewing the at least one picture and accompanying description of the at least one item being sold on the item description web page (3W1);
• using a user terminal (1) to link to a seller blog (31) for viewing the at least one picture and accompanying description of the at least one item being sold on the item description web page (3W1);
• and
• clicking the payment tab on the item description web page (3W1) to start a payment procedure;
• at a sales agent:
• using a sales agent terminal (22) to link to a sales agent blog (32);
• creating a plurality of item web pages (3W2) in the sales agent blog (32) for selling the at least one item posted on the item description web page (3W1) with the at least one picture and accompanying description of the at least one item being sold on the item description web page (3W1) are further posted on the item web page (3W2);
• using the sales agent terminal (22) to link to a platform server (41);
• applying for membership;
• gaining access to the platform server (41);
• linking to the login server (42);
• logging in for gaining access to the program database (461);
• copying the program codes of the sales agent tab program (P1) to the sales agent terminal (22);
• using the sales agent terminal (22) to link to the sales agent blog (32);
• copying the program codes of the sales agent tab program (P1) to the sales agent blog (32);
• installing the guide tab, the payment tab, and the program codes of the sales agent tab program (P1) in the item web page (3W2);
• using the sales agent terminal (22) to link to the platform server (41) and further to the login server (42);
• logging in for obtaining the tab program codes (PC) by linking to the program database (461);
• and
• using the sales agent terminal (22) to link to the sales agent blog (32) and copy the tab program codes (PC) to the sales agent blog (32);
• at the buyer:
• using the user terminal (1) to link to the sales agent blog (32) for viewing the at least one picture and accompanying description of the at least one item being sold on the item web page (3W2);
• at the seller:
• using the seller terminal (21) to link to the platform server (41) and the login server (42);
• logging in to link to an e-mail server (45) of the online billing platform (4);
• sending a client file to a client database (452) of the e-mail server (45);
• creating a client record file (452D) in the client database (452);
• creating an advertisements issuing web page (45W) in the e-mail server (45) of the online billing platform (4) based on the client record file (452D) and the merchandise file (431D);
• using the seller terminal (21) to link to the platform server (41) and the login server (42);
• logging in for linking to the advertisements issuing web page (45W);
• inputting a client list and information about merchandise being sold on the advertisements issuing web page (45W);
• creating an issued advertisements file (453D) in an advertisement database (453) of the e-mail server (45) based on the client list and the information about merchandise being sold;
• and
• enabling the e-mail server (45) to send an e-mail including the payment tab and the issued advertisements file (453D) to the buyer;
• at the buyer:
• buying an item being sold on the item web page (3W2) by clicking the payment tab of the item web page (3W2) which is in turn linked to the platform server (41) and the login server (42);
• logging in for linking to a payment web page (44W1) of a billing server (44) of the online billing platform (4);
• inputting payment data on the payment web page (44W1);
• and
• creating a purchase order file with order number (441D) in a purchase order database (441) of the billing server (44) based on the payment data;
• linking the platform server (41) to a bank terminal (5);
• enabling the billing server (44) to verify credit card information provided in the purchase order file with order number (441D) with a credit card issuing bank;
• creating a transaction particulars file with order number (442D) in a bank database (442) of the billing server (44) based on an authorization from the credit card issuing bank;
• creating a shipment file with order number (443D) in a shipment database (443) of the billing server (44);
• enabling the e-mail server (45) to send an e-mail including the purchase order file with order number (441D) to the buyer;
• and
• enabling the e-mail server (45) to send an e-mail to the seller to prepare the bought item and ship same based on the shipment file with order number (443D);
• at the sales agent:
• after the shipment, using the sales agent terminal (22) to link to the platform server (41) and the login server (42);
• logging in for linking to a request for payment web page (44W2) of the billing server (44);
• inputting request for payment data on the request for payment web page (44W2);
• and
• creating a debit note file with order number (444D) in a request for payment database (444) of the billing server (44) based on the request for payment data;
• and
• after being verified by a manager of the online billing platform (4), preparing an invoice and sending same to the buyer for request for payment.

A method of online shopping comprising the steps of:

• at a seller:
• using a seller terminal (23) to access a seller blog (33) over the Internet (6);
• and
• creating a first item description web page (3W1) in the seller blog (33) wherein at least one picture and accompanying description of at least one item being sold are posted on the first item description web pages (3W1);
• at a reseller:
• using a reseller terminal (24) to access a reseller blog (34) over the Internet (6);
• and
• creating a second item description web page (3W1) in the reseller blog (34) wherein at least one picture and accompanying description of at least one item being sold are posted on the second item description web page (3W1);
• at a manager of an online billing platform (4):
• manufacturing at least one OEM product based on a combination of the at least one item posted on the first item description web page (3W1) and the at least one item posted on the second item description web page (3W1);
• and
• creating an OEM merchandise file (431D) in a merchandise database (431);
• creating tab program codes (PC) in a program database (461);
• creating a plurality of OEM merchandise sale web pages (43W2) by the OEM merchandise file (431D) wherein each of the OEM merchandise sale web pages (43W2) includes a payment tab, a first link tab, and a second link tab;
• at a buyer:
• clicking the first link tab of the OEM merchandise sale web pages (43W2) to link a platform server (41) of the online billing platform (4) to the first item description web page (3W1) for viewing the at least one picture and accompanying description of the at least one item being sold on the first item description web page (3W1);
• and
• clicking the second link tab of the OEM merchandise sale web pages (43W2) to link the platform server (41) to the second item description web page (3W1) for viewing the at least one picture and accompanying description of the at least one item being sold on the second item description web page (3W1);
• at the seller:
• using the seller terminal (23) to link to a seller blog (33);
• creating a first OEM merchandise web page (3W3) in the seller blog (33) wherein at least one picture and accompanying description of at least one item being sold are posted on the first OEM merchandise web page (3W3);
• using the seller terminal (23) to link to the platform server (41) and a member web page (42W) of a login server (42) of the online billing platform (4);
• applying for membership;
• using the seller terminal (23) to access the platform server (41);
• linking to the login server (42);
• logging in for gaining access to a program database (461);
• copying program codes of an OEM tab program (P2) to the seller terminal (23);
• copying the program codes of the OEM tab program (P2) to the seller blog (33);
• installing a purchase confirmation tab, a guide tab, and the program codes of the OEM tab program (P2) in the first OEM merchandise web page (3W3);
• logging in for obtaining the tab program codes (PC) by linking to the program database (461);
• using the seller terminal (23) to link to the seller blog (33) and copy the tab program codes (PC) to the seller blog (33);
• and
• linking the first OEM merchandise web page (3W3) to the platform server (41) and the OEM merchandise sale web page (43W2);
• at the buyer:
• using a user terminal (1) to link to the seller blog (33) for viewing the at least one picture and accompanying description of the at least one item being sold on the first OEM merchandise web page (3W3);
• clicking the purchase confirmation tab on the first OEM merchandise web page (3W3);
• linking the first OEM merchandise web page (3W3) to the platform server (41) and the OEM merchandise sale web pages (43W2);
• and
• buying one or more OEM items posted on the OEM merchandise sale web pages (43W2) by clicking the payment tab thereon;
• at the reseller:
• using the reseller terminal (24) to link to the reseller blog (34);
• creating a second OEM merchandise web page (3W3) in the reseller blog (34) wherein at least one picture and accompanying description of at least one item being sold are posted on the second OEM merchandise web page (3W3);
• using the reseller terminal (24) to link to the platform server (41) and the member web page (42W);
• applying for membership;
• using the reseller terminal (24) to link to the platform server (41) and the login server (42);
• logging in for gaining access to the program database (461);
• copying the program codes of the OEM tab program (P2) to the reseller terminal (24);
• copying the program codes of the OEM tab program (P2) to the reseller blog (34);
• installing the purchase confirmation tab, the guide tab, and the program codes of the OEM tab program (P2) in the second OEM merchandise web page (3W3);
• logging in for obtaining the tab program codes (PC) by linking to the program database (461);
• copying the tab program codes (PC) to the reseller blog (34);
• clicking the purchase confirmation tab on the second OEM merchandise web page (3W3);
• linking the second OEM merchandise web page (3W3) to the platform server (41) and the OEM merchandise sale web pages (43W2);
• and
• buying one or more OEM items posted on the OEM merchandise sale web pages (43W2) by clicking the payment tab thereon;
• using the user terminal (1) to link to the reseller blog (34) for viewing the at least one picture and accompanying description of the at least one item being sold on the second OEM merchandise web page (3W3);
• buying an OEM item sold on the second OEM merchandise web page (3W3) by clicking the purchase confirmation tab on the second OEM merchandise web page (3W3) which is in turn linked to the platform server (41) and the OEM merchandise sale web pages (43W2);
• and
• clicking the purchase confirmation tab on the second OEM merchandise web page (3W3) to link to the platform server (41) and the login server (42);
• at the buyer:
• logging in for linking to a payment web page (44W1) of a billing server (44) of the online billing platform (4);
• and
• inputting payment data on the payment web page (44W1);
• creating a purchase order file with order number (441D) in a purchase order database (441) of the billing server (44) based on the payment data;
• linking the platform server (41) to a bank terminal (5);
• enabling the billing server (44) to verify credit card information provided in the purchase order file with order number (441D) with a credit card issuing bank;
• creating a transaction particulars file with order number (442D) in a bank database (442) of the billing server (44) based on an authorization from the credit card issuing bank;
• creating a shipment file with order number (443D) in a shipment database (443) of the billing server (44);
• enabling the e-mail server (45) to send an e-mail including the purchase order file with order number (441D) to the buyer;
• and
• enabling the e-mail server (45) to send an e-mail to the seller to prepare the bought OEM item and ship same to the reseller based on the shipment file with order number (443D);
• enabling the e-mail server (45) to send an e-mail to the reseller to manufacture the bought OEM item after receiving the OEM item from the seller based on the shipment file with order number (443D);
• at the reseller:
• shipping the manufactured OEM item to the buyer based on the shipment file with order number (443D);
• at the seller:
• after the shipment, using the seller terminal (23) to link to the platform server (41) and the login server (42);
• logging in for linking to a request for payment web page (44W2) of the billing server (44);
• inputting request for payment data on the request for payment web page (44W2);
• and
• creating a debit note file with order number (444D) in a request for payment database (444) of the billing server (44) based on the request for payment data;
• at the reseller:
• after the shipment, using the reseller terminal (24) to link to the platform server (41) and the login server (42);
• logging in for linking to a request for payment web page (44W2) of the billing server (44);
• inputting request for payment data on the request for payment web page (44W2);
• and
• creating a debit note file with order number (444D) in a request for payment database (444) of the billing server (44) based on the request for payment data;
• and
• after being verified by the manager of the online billing platform (4), preparing an invoice and sending same to the buyer for request for payment.