1 00:00:13,650 --> 00:00:16,832 Hello, I’m Sung Hyun Yoon, and I’ll be leading the Order Process session 2 00:00:17,030 --> 00:00:19,775 of the SERVEONE MRO Process course 3 00:00:20,280 --> 00:00:23,003 Today’s lecture focuses on the order process 4 00:00:23,330 --> 00:00:25,746 within the overall workflow 5 00:00:26,370 --> 00:00:28,996 The goals of this session are: 6 00:00:29,749 --> 00:00:32,942 To understand the order process within SERVEONE 7 00:00:33,279 --> 00:00:36,644 To distinguish the characteristics of each order method 8 00:00:37,079 --> 00:00:41,515 To identify what can be changed after an order is created 9 00:00:42,040 --> 00:00:47,792 In the FAQ session, we’ll cover most common topic among sales, operations, and managers, 10 00:00:48,040 --> 00:00:51,472 pre-receipt eligible documentation 11 00:00:51,769 --> 00:00:53,531 I’ll explain why this documentation needs to be managed 12 00:00:53,828 --> 00:00:57,778 and what information must be included 13 00:01:00,360 --> 00:01:02,391 First, let me introduce myself 14 00:01:02,559 --> 00:01:04,770 I’m a dad of a three-month-old daughter, 15 00:01:04,770 --> 00:01:06,813 enjoying a very happy daily life these days 16 00:01:07,239 --> 00:01:10,441 My hobby is playing badminton 17 00:01:10,599 --> 00:01:12,569 I’ve been with SERVEONE for eight years 18 00:01:12,569 --> 00:01:17,187 and currently handle operations system management and planning 19 00:01:18,879 --> 00:01:20,493 Order process Overview 20 00:01:20,800 --> 00:01:23,715 To briefly explain the SERVEONE order process, 21 00:01:24,170 --> 00:01:26,559 it can be illustrated as shown in the flowchart 22 00:01:27,579 --> 00:01:29,350 So, what is an order? 23 00:01:29,409 --> 00:01:31,150 By definition 24 00:01:31,279 --> 00:01:33,299 it is a request made to a seller 25 00:01:33,299 --> 00:01:38,156 to produce, deliver, or provide a product or service 26 00:01:38,763 --> 00:01:41,246 In today’s session, I’ll explain 27 00:01:41,919 --> 00:01:45,734 how a customer requests a product from SERVEONE 28 00:01:46,170 --> 00:01:49,351 and how the order process flows within SERVEONE 29 00:01:49,420 --> 00:01:51,671 I'm going to explain these 30 00:01:52,899 --> 00:01:55,389 First, when a customer visits SERVEONE Mall, 31 00:01:55,389 --> 00:01:59,503 they search for products, add them to the cart, and confirm the purchase 32 00:01:59,859 --> 00:02:03,103 After completing internal approval, the order is finalized 33 00:02:03,519 --> 00:02:06,599 Alternatively, when SERVEONE receives a customer order, 34 00:02:06,599 --> 00:02:12,400 it runs a simulation based on a preset logic 35 00:02:12,400 --> 00:02:15,891 that considers price, product characteristics, items, and regions 36 00:02:16,039 --> 00:02:17,967 Then, a purchase order is issued to the supplier 37 00:02:18,759 --> 00:02:23,419 For direct-shipment, no-stock orders, 38 00:02:23,419 --> 00:02:25,402 the supplier ships the products directly 39 00:02:25,679 --> 00:02:28,651 After the S/O (Sales Order) is created, 40 00:02:28,928 --> 00:02:33,261 for Center VMI orders, 41 00:02:33,479 --> 00:02:36,360 the hub ships the products stored in its own inventory 42 00:02:37,360 --> 00:02:40,693 At set intervals, transactions related to deliveries 43 00:02:41,020 --> 00:02:42,760 are settled, 44 00:02:42,760 --> 00:02:45,654 finalizing receivables and payables through 45 00:02:46,109 --> 00:02:47,801 purchase settlement with suppliers 46 00:02:48,039 --> 00:02:50,795 and sales settlement with customers 47 00:02:51,399 --> 00:02:56,939 Afterward, any orders not financially realized are handled as exceptions 48 00:02:57,800 --> 00:03:00,515 Do you have a general understanding of the SERVEONE order process? 49 00:03:00,960 --> 00:03:03,659 Next, we’ll break it down 50 00:03:03,659 --> 00:03:09,118 to review each concept and basic workflow 51 00:03:10,019 --> 00:03:12,129 Refer to the process diagram 52 00:03:12,129 --> 00:03:15,176 to help you understand it better 53 00:03:15,800 --> 00:03:20,182 When a customer places an order and SERVEONE’s S/O is created, 54 00:03:20,479 --> 00:03:23,892 the delivery method is determined through the order simulation, 55 00:03:24,229 --> 00:03:27,039 and the supplier or hub ships the products 56 00:03:28,010 --> 00:03:29,823 Once the delivery is complete, 57 00:03:30,130 --> 00:03:33,880 purchase settlement with the supplier and sales settlement with the customer are processed, 58 00:03:33,880 --> 00:03:35,812 completing the order process 59 00:03:36,440 --> 00:03:39,470 Order creation simply means that 60 00:03:39,470 --> 00:03:43,024 a customer places an order with SERVEONE 61 00:03:43,559 --> 00:03:47,342 In daily life, when we want to buy something, 62 00:03:47,639 --> 00:03:50,617 there are various ways to place an order 63 00:03:51,320 --> 00:03:53,691 Visiting a store in person, 64 00:03:53,849 --> 00:03:56,091 shopping online, 65 00:03:56,240 --> 00:04:00,265 or requesting through a delivery service, and so on 66 00:04:00,839 --> 00:04:05,652 There are several ways for customers to create orders with SERVEONE 67 00:04:05,919 --> 00:04:08,934 We’ll cover four main methods 68 00:04:10,320 --> 00:04:12,480 When the customer places an order directly 69 00:04:12,480 --> 00:04:15,705 through the SERVEONE Mall, it’s called a Front Order 70 00:04:16,160 --> 00:04:18,862 When the customer places an order directly 71 00:04:19,089 --> 00:04:22,770 but through their own system, 72 00:04:22,800 --> 00:04:24,274 it’s called an Integrated Order 73 00:04:24,799 --> 00:04:27,010 When the customer requests offline 74 00:04:27,010 --> 00:04:29,122 and SERVEONE creates the order first, 75 00:04:29,399 --> 00:04:33,207 with delivery starting immediately, it’s called a Proxy Order 76 00:04:33,920 --> 00:04:36,462 When the customer requests offline 77 00:04:36,670 --> 00:04:38,822 and SERVEONE creates the order, 78 00:04:39,000 --> 00:04:41,725 but delivery is arranged in advance, it’s called a Pre-Receipt Order 79 00:04:42,279 --> 00:04:46,102 The first method is the Customer Front Order, the most common way to place an order 80 00:04:46,310 --> 00:04:49,866 The customer orders on the SERVEONE Mall, 81 00:04:50,519 --> 00:04:52,379 The customer selects products, 82 00:04:52,379 --> 00:04:56,372 adds them to the cart, and places the order, 83 00:04:56,679 --> 00:04:59,210 the system then checks for credit and budget limits 84 00:04:59,279 --> 00:05:01,652 If there are no issues, the order is created, 85 00:05:01,880 --> 00:05:04,839 and after internal approval, the final S/O is generated 86 00:05:05,799 --> 00:05:08,792 SERVEONE Mall is where we purchase office supplies 87 00:05:09,079 --> 00:05:12,379 Here, the customer searches for products, 88 00:05:12,379 --> 00:05:14,848 adds them to the cart, and places an order 89 00:05:16,319 --> 00:05:18,160 Once the order is created, 90 00:05:18,160 --> 00:05:21,039 a message saying “Order has been created” appears, 91 00:05:21,039 --> 00:05:23,595 confirming that the order was successfully placed 92 00:05:24,239 --> 00:05:26,339 The second method is the Customer Integrated Order 93 00:05:26,339 --> 00:05:29,522 When the customer creates an order in their own system, 94 00:05:29,865 --> 00:05:32,859 the order is automatically transferred to the SERVEONE system, 95 00:05:32,859 --> 00:05:36,344 and an S/O is generated there 96 00:05:36,908 --> 00:05:39,251 The only difference between Front Orders and Integrated Orders 97 00:05:39,409 --> 00:05:42,449 is the site used to place the order 98 00:05:42,449 --> 00:05:44,732 either the SERVEONE Mall or the customer’s system 99 00:05:44,920 --> 00:05:48,594 In terms of process, they are essentially the same 100 00:05:49,139 --> 00:05:51,999 The third order type is the Proxy Order, 101 00:05:51,999 --> 00:05:53,964 where SERVEONE’s role becomes more important 102 00:05:54,320 --> 00:05:57,400 In this method, the operations manager creates an order 103 00:05:57,400 --> 00:06:02,256 in the SERVEONE system based on the customer’s request data 104 00:06:02,880 --> 00:06:06,940 Orders handled this way start with 700 in the SERVEONE order number, 105 00:06:06,940 --> 00:06:12,217 and SSP proxy orders start with 400 106 00:06:12,880 --> 00:06:15,934 This method is not available to all customers 107 00:06:16,340 --> 00:06:19,170 and is only allowed for those who have signed 108 00:06:19,170 --> 00:06:21,498 a Proxy Order Agreement with SERVEONE 109 00:06:22,320 --> 00:06:26,792 In this process, when a customer requests an order offline, 110 00:06:26,881 --> 00:06:30,673 the operations manager first reviews the attached documents 111 00:06:30,930 --> 00:06:33,123 to check if they meet internal eligibility standards 112 00:06:33,559 --> 00:06:38,391 Only with valid documentation, operations manager create the order in the SERVEONE system 113 00:06:38,579 --> 00:06:41,382 After that, the system checks credit and budget approvals, 114 00:06:41,600 --> 00:06:44,798 and if there are no issues, the order is successfully created 115 00:06:45,550 --> 00:06:49,361 Compared to regular Front Orders, 116 00:06:49,519 --> 00:06:52,950 Proxy Orders require more work, 117 00:06:52,950 --> 00:06:55,072 such as document review and manual order creation in the system 118 00:06:55,399 --> 00:06:57,781 However, based on the customer’s situation, 119 00:06:57,989 --> 00:07:01,542 they are carried out by internal decisions 120 00:07:01,839 --> 00:07:06,347 You might be wondering how operations managers actually create proxy orders 121 00:07:07,640 --> 00:07:10,241 This process will be explained in the video, 122 00:07:10,409 --> 00:07:16,222 which shows tasks automated through RPA, recorded as the PC performs them automatically 123 00:07:16,978 --> 00:07:22,728 Log in to S-Portal 124 00:07:27,888 --> 00:07:31,638 Check the proxy order emails in the unread mailbox 125 00:07:33,083 --> 00:07:41,333 Save the documents and request files 126 00:07:43,494 --> 00:07:51,144 Log in to S-MRO 127 00:07:58,270 --> 00:08:03,670 Search operating units 128 00:08:04,074 --> 00:08:21,274 Download the registered delivery address information 129 00:08:21,867 --> 00:08:26,467 Compare the order request form with the delivery data to extract new addresses 130 00:08:26,602 --> 00:08:34,752 Search postal codes (1st: Korea Post App) 131 00:08:35,832 --> 00:08:43,782 Search postal codes (2nd: Daum) 132 00:08:44,703 --> 00:08:50,303 Search postal codes (3rd: Road name address) 133 00:08:50,956 --> 00:08:53,456 Generate the S-MRO bulk upload file for new addresses 134 00:08:55,469 --> 00:08:57,819 Log in to S-MRO 135 00:09:01,508 --> 00:09:16,508 Bulk register the new delivery addresses 136 00:09:17,389 --> 00:09:26,189 Download the updated delivery address data 137 00:09:26,337 --> 00:09:34,837 Compare it with the order request form to create the proxy order upload file 138 00:09:38,555 --> 00:09:41,955 Search operating units and member IDs 139 00:09:44,632 --> 00:09:48,798 Upload the documents and proxy order file 140 00:09:48,798 --> 00:09:50,498 Create the order 141 00:09:51,579 --> 00:09:59,929 Check the order status 142 00:10:00,390 --> 00:10:05,090 Generate the result file 143 00:10:06,482 --> 00:10:08,282 Log in to S-Portal 144 00:10:11,024 --> 00:10:20,375 Send an email with the RPA results to the responsible manager 145 00:10:23,020 --> 00:10:25,213 Lastly, we have Pre-Receipt 146 00:10:25,520 --> 00:10:28,980 This applies to customers with a signed agreement 147 00:10:28,980 --> 00:10:33,893 and happens before the system order is created, based on the customer’s request 148 00:10:34,200 --> 00:10:38,524 It’s divided into pre-receipt order and pre-receipt processing 149 00:10:38,880 --> 00:10:42,322 When the customer hasn't received the product yet, it's pre-receipt order 150 00:10:42,480 --> 00:10:47,078 When the customer has already received the product, it's pre-receipt processing 151 00:10:47,840 --> 00:10:52,550 As the term “processing” implies, this type handles cases where the delivery is already completed, 152 00:10:52,550 --> 00:10:56,527 and the system update is done afterward 153 00:10:57,200 --> 00:11:01,590 To clarify the difference between Pre-Receipt Orders 154 00:11:01,590 --> 00:11:03,113 and Proxy Orders, 155 00:11:03,420 --> 00:11:06,422 Proxy Orders follow the normal process, 156 00:11:06,610 --> 00:11:11,151 but the order is created by SERVEONE instead of the customer 157 00:11:11,359 --> 00:11:15,129 In contrast, Pre-Receipt Orders are also created by SERVEONE, 158 00:11:15,179 --> 00:11:18,809 but they’re a non-standard process, orders can be created 159 00:11:18,849 --> 00:11:21,289 even without budget approval or internal authorization 160 00:11:21,289 --> 00:11:24,099 Think of them as an exception type outside the normal workflow 161 00:11:24,980 --> 00:11:28,920 Pre-Receipt Orders and Pre-Receipt Processing are further classified 162 00:11:28,920 --> 00:11:32,876 based on who makes the request and who creates the request in the system 163 00:11:33,440 --> 00:11:35,620 If the customer requests directly from the supplier, 164 00:11:35,620 --> 00:11:41,043 and the supplier submits it through the supplier portal, it’s called Supplier Pre-Receipt Processing 165 00:11:41,350 --> 00:11:46,742 If the customer requests through sales or operations, 166 00:11:46,910 --> 00:11:49,312 and operations submit it in S-MRO, it’s called Sales Pre-Receipt Processing 167 00:11:50,579 --> 00:11:53,784 Do you see the section marked in red that says “Supplier Selection”? 168 00:11:54,269 --> 00:11:56,449 As we’ll cover again in the FAQ, 169 00:11:56,449 --> 00:12:00,180 since Pre-Receipt Processing happens after the product is already delivered, 170 00:12:00,319 --> 00:12:04,559 the actual supplier who handled it must be specified 171 00:12:05,668 --> 00:12:08,711 Let's look closer at Pre-Receipt Orders and Pre-Receipt Processing 172 00:12:08,919 --> 00:12:13,540 For Pre-Receipt Orders, the order is registered first, and the product is delivered afterward 173 00:12:13,689 --> 00:12:17,609 For Pre-Receipt Processing, the customer requests delivery in advance, 174 00:12:17,609 --> 00:12:20,039 receives the product first, 175 00:12:20,039 --> 00:12:24,456 and the system order is created later 176 00:12:25,080 --> 00:12:28,922 Also, for both types, before the order can be marked as delivery completed, 177 00:12:29,140 --> 00:12:33,726 the customer must perform a Pre-Receipt Order Confirmation 178 00:12:34,439 --> 00:12:37,692 This confirmation step is unique to Pre-Receipt 179 00:12:37,959 --> 00:12:42,459 and serves as a verification process between the customer and SERVEONE 180 00:12:42,459 --> 00:12:46,044 to confirm how many products were pre-received and that they were indeed delivered 181 00:12:47,460 --> 00:12:50,657 Wondering when Pre-Receipt is used? 182 00:12:51,320 --> 00:12:54,920 Pre-Receipt is a non-standard process 183 00:12:54,920 --> 00:12:57,283 used when products are urgently needed 184 00:12:57,748 --> 00:13:00,280 It’s mainly applied when there’s an urgent delivery request 185 00:13:00,280 --> 00:13:04,362 or when the customer’s internal approval is delayed 186 00:13:04,540 --> 00:13:08,604 This means an order can be created even without budget or approval 187 00:13:09,799 --> 00:13:14,143 Because of this, SERVEONE managers need to be extra cautious 188 00:13:14,499 --> 00:13:17,222 Since orders can be created even with a negative budget, 189 00:13:17,539 --> 00:13:19,259 you must ensure there are 190 00:13:19,259 --> 00:13:22,901 no cancellations or returns due to budget issues after creating a Pre-Receipt Order 191 00:13:23,020 --> 00:13:25,960 Also, when processing Pre-Receipts, if the order is placed with a different supplier 192 00:13:25,960 --> 00:13:30,170 instead of the designated Pre-Receipt supplier, it can cause duplicate orders, 193 00:13:30,170 --> 00:13:31,568 so extra caution is needed 194 00:13:32,320 --> 00:13:36,418 Lastly, since settlement is only possible after the customer’s Pre-Receipt approval is completed, 195 00:13:36,705 --> 00:13:40,557 you must always check the approval status to avoid any sales settlement issues 196 00:13:41,919 --> 00:13:46,300 The smart RPA introduced earlier for Proxy Orders 197 00:13:46,419 --> 00:13:48,351 is also used for Pre-Receipt Processing 198 00:13:48,509 --> 00:13:52,290 Let’s watch a video to see how Pre-Receipt processing works 199 00:18:04,199 --> 00:18:07,389 So far, we’ve covered the four order creation methods in SERVEONE 200 00:18:07,389 --> 00:18:11,839 Front Orders, Integrated Orders, Proxy Orders, and Pre-Receipt Orders/Processing 201 00:18:11,839 --> 00:18:14,863 We\'ve learned about these things 202 00:18:15,229 --> 00:18:18,291 Next, we’ll move on to order modifications 203 00:18:19,119 --> 00:18:23,311 Order modification covers what can be changed and managed 204 00:18:23,549 --> 00:18:26,129 from the time a customer places an order 205 00:18:26,129 --> 00:18:28,105 until delivery is completed 206 00:18:28,640 --> 00:18:31,761 Although the actual changes are handled by the operations manager, 207 00:18:31,890 --> 00:18:35,222 it’s important to understand what can be modified and how 208 00:18:35,400 --> 00:18:38,560 Knowing this will help with internal and external communication, 209 00:18:38,560 --> 00:18:40,727 so I’ll give you a brief explanation 210 00:18:41,479 --> 00:18:45,124 First, let’s look at the overall order management types 211 00:18:45,688 --> 00:18:49,279 Order management can be divided into three categories 212 00:18:49,279 --> 00:18:51,425 Customer-related, supplier-related, and internal tasks 213 00:18:51,920 --> 00:18:58,084 Customer-related tasks include handling order cancellation, returns, and exchanges/AS, 214 00:18:58,440 --> 00:19:01,426 following up on customer system inquiries, managing urgent delivery requests 215 00:19:02,040 --> 00:19:04,141 Supplier-related tasks include 216 00:19:04,270 --> 00:19:09,266 handling supplier requests, managing partial deliveries, checking purchase order details and delivery schedules 217 00:19:09,959 --> 00:19:16,319 Internal tasks include managing integration error orders, verifying POs, handling delivery proofs and basic docs 218 00:19:16,319 --> 00:19:19,572 These are the main tasks 219 00:19:20,780 --> 00:19:23,922 The scope of order management is very broad, 220 00:19:24,160 --> 00:19:28,290 but here we’ll focus only on a few items that can be modified 221 00:19:28,290 --> 00:19:30,479 in the order inquiry screen 222 00:19:31,479 --> 00:19:33,759 Most customer-related changes 223 00:19:33,759 --> 00:19:36,772 can be handled here 224 00:19:37,099 --> 00:19:39,413 Customer information 225 00:19:39,839 --> 00:19:45,441 Shipping address, cost, department, purchase reason, and reference codes 226 00:19:45,659 --> 00:19:48,109 These can be changed 227 00:19:49,040 --> 00:19:52,740 You can also update approver information in the SERVEONE system 228 00:19:52,740 --> 00:19:55,839 when the customer’s internal approver changes 229 00:19:56,760 --> 00:20:01,340 In addition, you can modify the sales information for an order, 230 00:20:01,419 --> 00:20:08,367 such as currency (KRW, USD, etc.) and distribution channel, including doemstic, local, direct or indirect export 231 00:20:09,120 --> 00:20:12,248 For integrated customers, any changes made in the customer’s system 232 00:20:12,248 --> 00:20:15,911 are not updated in real time for orders that have already been created 233 00:20:16,168 --> 00:20:20,940 In such cases, details like the PR number or PO number 234 00:20:21,059 --> 00:20:22,826 can be manually updated in the order 235 00:20:24,360 --> 00:20:28,984 You can also attach files to an order, not just update text fields 236 00:20:29,380 --> 00:20:31,460 Attaching files 237 00:20:31,460 --> 00:20:36,176 helps streamline communication between the customer, supplier, and SERVEONE 238 00:20:36,839 --> 00:20:42,200 Through these order management features, you can handle customer requests 239 00:20:44,400 --> 00:20:47,380 Next, we’ll briefly talk about Pre-Receipt documentation, 240 00:20:47,380 --> 00:20:51,200 a topic that often comes up in inquiries 241 00:20:51,200 --> 00:20:53,064 After that, we’ll wrap up today’s session 242 00:20:54,040 --> 00:20:57,425 What if Pre-Receipt is handled without documentation and only through verbal requests? 243 00:20:57,900 --> 00:21:01,021 It could lead to communication errors, 244 00:21:01,021 --> 00:21:02,584 wrong products delivered, incorrect quantities, 245 00:21:03,000 --> 00:21:07,320 or even duplicate orders if the request 246 00:21:07,320 --> 00:21:10,565 goes to the wrong supplier 247 00:21:11,199 --> 00:21:14,651 To minimize future issues 248 00:21:14,859 --> 00:21:17,941 and keep proper records, 249 00:21:18,020 --> 00:21:20,083 documentation is essential 250 00:21:20,360 --> 00:21:24,541 Sales and operations managers must also be able to 251 00:21:24,749 --> 00:21:29,290 review customer-provided documents and judge whether they are valid and risk-free 252 00:21:30,280 --> 00:21:33,860 The purpose of Pre-Receipt documentation 253 00:21:33,860 --> 00:21:37,950 is to clearly confirm the customer’s request and delivery status 254 00:21:37,950 --> 00:21:42,437 when products are supplied or requested before a system order is created 255 00:21:43,239 --> 00:21:48,021 For both Pre-Receipt Orders and Pre-Receipt Processing, you must verify what products 256 00:21:48,209 --> 00:21:50,132 and how many were requested 257 00:21:50,479 --> 00:21:53,448 For Pre-Receipt Processing, you must also confirm 258 00:21:53,448 --> 00:21:57,148 whether the products were actually delivered through the specified supplier 259 00:21:58,280 --> 00:22:01,032 By verifying these details with proper documentation 260 00:22:01,240 --> 00:22:03,401 before creating the system order, 261 00:22:03,569 --> 00:22:06,438 you can prevent settlement issues later on 262 00:22:07,221 --> 00:22:10,882 The required documents vary depending on the request channel 263 00:22:11,090 --> 00:22:13,700 The goal is to minimize creating separate documents 264 00:22:13,700 --> 00:22:16,416 and instead use existing data whenever possible 265 00:22:17,000 --> 00:22:19,500 For example, you can use the customer’s Pre-Receipt form, 266 00:22:19,500 --> 00:22:23,441 closing documents, weighing slips, or interface-linked data 267 00:22:23,639 --> 00:22:26,248 as valid Pre-Receipt documentation 268 00:22:26,941 --> 00:22:29,350 From this page through the next nine pages, 269 00:22:29,350 --> 00:22:33,133 you’ll find explanations of the different Pre-Receipt proof types, 270 00:22:33,479 --> 00:22:38,088 including real case examples, required fields, and important notes or exceptions 271 00:22:38,920 --> 00:22:41,254 This is the basic Pre-Receipt request form 272 00:22:41,690 --> 00:22:46,390 As shown in the example, it must include the following required fields 273 00:22:46,390 --> 00:22:48,957 customer name, requester, signature, supplier, 274 00:22:49,393 --> 00:22:52,243 product name, quantity, and specifications 275 00:22:52,560 --> 00:22:55,050 If the same proof is provided as an Excel file, 276 00:22:55,050 --> 00:22:57,171 its content can be modified, 277 00:22:57,310 --> 00:23:00,610 so you must verify separately, via email or another method 278 00:23:00,610 --> 00:23:03,727 that the customer actually requested the order with those details 279 00:23:04,479 --> 00:23:08,201 Next is a VOC Pre-Receipt case received through the customer front 280 00:23:08,379 --> 00:23:13,561 In this case, since the system already confirms the customer’s request or receipt, 281 00:23:13,759 --> 00:23:18,349 you only need to verify the product and quantity without requiring any additional documents 282 00:23:20,439 --> 00:23:22,675 The next case involves a supplier transaction statement 283 00:23:23,249 --> 00:23:27,754 The statement must include the product name and quantity, 284 00:23:28,308 --> 00:23:31,829 and you must also confirm which customer actually received the products 285 00:23:31,829 --> 00:23:34,151 through the customer’s signature 286 00:23:35,319 --> 00:23:37,947 Next is the customer Pre-Receipt request form 287 00:23:38,630 --> 00:23:42,100 Regardless of the template used, it must include product information, 288 00:23:42,289 --> 00:23:47,781 and after obtaining the customer’s signed confirmation, the supplier’s name must also be specified 289 00:23:48,880 --> 00:23:51,005 The next case is the customer’s closing documents 290 00:23:51,500 --> 00:23:56,811 In the email agreed upon with the customer, make sure the closing data or receipt details are mentioned, 291 00:23:56,989 --> 00:24:02,260 and confirm that the document includes all necessary information, such as product name, ID, and quantity, 292 00:24:02,260 --> 00:24:03,938 to enable order creation in the system 293 00:24:04,829 --> 00:24:09,982 A weighing slip can be used as proof of delivery by attaching a screenshot of the slip 294 00:24:10,199 --> 00:24:12,582 However, since it lacks order details, 295 00:24:12,859 --> 00:24:15,280 you must also include additional information such as 296 00:24:16,320 --> 00:24:19,889 requester, product name, product ID, and order quantity 297 00:24:21,719 --> 00:24:24,014 This is the Pre-Receipt interface screen 298 00:24:24,469 --> 00:24:30,350 For certain customers, if Pre-Receipt data is received through the interface from the customer’s system, 299 00:24:30,518 --> 00:24:33,672 that data itself is considered valid documentation 300 00:24:33,959 --> 00:24:37,490 In this case, the interface data can replace the customer’s signature, 301 00:24:37,648 --> 00:24:41,516 but you must ensure that all required fields are properly included 302 00:24:42,759 --> 00:24:46,469 Alright, we’ve now covered the key topics 303 00:24:46,469 --> 00:24:50,522 Order creation methods, order management, and Pre-Receipt documentation 304 00:24:50,839 --> 00:24:53,809 I hope this session helped you understand the basics 305 00:24:53,809 --> 00:24:55,390 Thank you for your time and effort 306 00:24:55,479 --> 00:24:56,150 Thank you